I know apple updated their policy related to sign in (see https://developer.apple.com/news/?id=f1v8pyay, "More flexibility for sign in options in apps" section), but the wording of the guidelines (https://developer.apple.com/app-store/review/guidelines/#login-services) is a bit difficult to understand: Apps that use a third-party or social login service (such as Facebook Login, Google Sign-In, Sign in with Twitter, Sign In with LinkedIn, Login with Amazon, or WeChat Login) to set up or authenticate the user’s primary account with the app must also offer as an equivalent option another login service with the following features: the login service limits data collection to the user’s name and email address; the login service allows users to keep their email address private as part of setting up their account; and the login service does not collect interactions with your app for advertising purposes without consent. As far as I can tell, FB, Google, Amazon, etc. do not offer these protections. Would Apple Sign In still be required in this case?

On my Xcode 12 beta simulators I am seeing several bugs when in limited photo access: Despite giving access to a subset of my photos (let's say 10 out of 100), when I call    PHFetchOptions *fetchOptions = [[PHFetchOptions alloc] init];   fetchOptions.sortDescriptors = @[[NSSortDescriptor sortDescriptorWithKey:@"creationDate" ascending:NO]];   PHFetchResult<PHAsset *> *accessibleAssets = [PHAsset fetchAssetsWithOptions:fetchOptions]; accessibleAssets contains all 100 of the simulator's photos. 2. When I display the limited library picker and make changes, the PHFetchResultChangeDetails object that is sent to the photoLibraryDidChange method does not contain any PHAsset objects in the result of the removedObjects, insertedObjects, or changedObjects so I'm not sure how I'm supposed to handle these changes if I need to take action on newly accessible/inaccessible photos. Both of these are reproducible on Xcode 12 betas 1 through 6. Is there any information on when these issues would be fixed? They are very difficult to deal with and are blocking me from releasing iOS 14 compatible updates to my application.

Hi there, In the app I work on, I am being tasked with a requirement to present the user their device photos using a PHPickerViewController. Once selected, I need access to: The raw image data The file name of the image The creation date of the image This is simple to do with a PHAsset if I had full access to the user's photos - I could use the PHPickerViewController result value which includes photoIdentifiers to query PhotoKit for the PHAssets. However, there is no guarantee that I have full access. Additionally if the user has granted no access or limited access, and the limited selection does not include the photos being selected in the PHPickerViewController, I won't be able to query for them. (I tried this, and as expected the result of the query is nil, which makes sense). The UIImage that I can obtain is only a proxy of the original image data (missing things like exif data, etc), so that is not sufficient for the user case my app has. Assuming there was an item provider for data, I'd still need to get information such as file name and creation date as well though. So, is there a way to obtain this information? Thanks!