I am getting the same error in my own app. Xcode 11.4.1, iPadOS 13.4.1, Objective-C, using a WKWebView to a videoplayer.See https://stackoverflow.com/a/58889528/872051 as well.
Post
Replies
Boosts
Views
Activity
The Objective-C way to get the assetIdentifier would be something like
(void)selectPressed:(id)sender{
		PHPhotoLibrary *photoLibrary = [PHPhotoLibrary sharedPhotoLibrary];
		PHPickerConfiguration *config = [[PHPickerConfiguration alloc] initWithPhotoLibrary: photoLibrary];
		config.selectionLimit = 1;
		config.filter = [PHPickerFilter videosFilter];
		PHPickerViewController *pickerViewController = [[PHPickerViewController alloc] initWithConfiguration:config];
		pickerViewController.delegate = self;
		[self presentViewController:pickerViewController animated:YES completion:nil];
}
(void)picker:(PHPickerViewController *)picker didFinishPicking:(NSArray<PHPickerResult *> *)results{
		[picker dismissViewControllerAnimated:YES completion:nil];	
		for (PHPickerResult *result in results) {
				NSArray *assetIdentifiers = @[result.assetIdentifier];
				PHFetchResult *assetResults = [PHAsset fetchAssetsWithLocalIdentifiers:assetIdentifiers options:nil];
				// Do something with the assetResults if you have Photos Library access
		}
}
It would be a good opportunity to reconsider if the app really needs direct Photos Library access or can work with just the image and video data. Is there any way to get the creation date of a video in the Photos Library without having direct access to it? The creation date of the picked result is not necessarily the same. Examples in a github project:
https://github.com/Jan-E/ikyle.me-code-examples/blob/master/Photo%20Picker%20ObjC/Photo%20Picker%20ObjC/PHPickerController.m#L223
We applied mid December and once again 3 weeks ago. No progress whatsoever.
Same issue over here. developer AT example.com got kicked. I changed the Apple-ID to jan.developer AT example.com and then it was accepted. Gmail users can add dots anywhere in the own name, so they should be able to do the same. But users at other domains might not have the same flexibility.
The release notes of 14.3.1 do not mention iOS 16.5, but if you try it support is there.