Similar here, but even worse! We are having more and more users who have the same issue after any kind of updates (os updates as well as app updates). The app shows the launch screen and then quits, no even calling didFinishLaunching. In same cases, the workaround is to send the app to icloud (offload) and then restart it, restoring all data from the cloud. Unfortunately, this worked fine in iOS 13 but does not always work in iOS 14.0. Currently, the only way to make the app work again is to delete and reinstall it, letting the user lose all of the data assign to the app. THIS IS A DESASTER for most of our users. We URGENTLY need a solution.

Having now submitted several privacy entitlement requests, I am receiving the following answers from Apple: "Thank you for your interest in the user-assigned device name entitlement. We need more information in order to review your request. Please review the entitlement documentation and provide screenshots of your app to show that the user-assigned device name is visible to the user." Well, I would have loved to upload that screenshot in the first place, but the application form did not provide a possibility for that. Now, that I still would love to upload that screenshot, Apple (still) does not tell me WHERE to upload it (the documentation page does not tell). Does someone else have this information? ;-)

Maybe your solution is here: https://stackoverflow.com/questions/70870182/app-store-connect-app-rejected-missing-purpose-strings-but-strings-exist-in-info

Same here. I used to list four file icons in CFBundleTypeIconFiles and forgot about them and deleted them. The file names are still listed in the CGBundleTypeIconFiles array, but there are no more files in the bundle. Interesting enough: it still works, but the system seems to create the icon itself (showing a small version of the app icon, below there is the file type - see below).

I ran into this, too. All betas that I posted by GitHub/XClode Cloud to TestFlight were marked as incompatible with Macs. Now, I fooled a little around and suddenly there was a version that was accepted as compatible, however, the issue was still reported by email (see above). What I did: Cleared the build folder Called dyld_info -platform /usr/lib/swift/libswiftCloudKit.dylib Added libswiftCloudKit.tdb to the framework list Removed the LSMinimumVersion key from the Info.plist I have no idea why this finally ended up in a working build, but it did. I assume that calling the dyld_info is the key.

Same here - for weeks. Tried not to use Xcode Cloud, uploaded the archives the old fashioned way. Same problem.