I have checked the logs when installing the app from Xcode and when installing it from TestFlight. The difference is that WidgetKit is not able to get a timeline from a widget when the app is installed from TestFlight. That is the reason why the widget is not available for selection. My best guess is that there is something wrong with signing on TestFlight server. From TestFlight: default 11:12:14.851813+1000 chronod [com.mr-brightside.myParcel.ParcelWidget:ParcelWidget:medium:-7973698613864559631@321.0/148.0/20.2] reload: begin default 11:12:14.856270+1000 chronod [myParcel.ParcelWidget-B81718B65DEC] Session operation: getTimeline request. default 11:12:14.928178+1000 chronod [myParcel.ParcelWidget-B81718B65DEC] Session operation: getTimeline error result: <private> error 11:12:14.928569+1000 chronod [com.mr-brightside.myParcel.ParcelWidget:ParcelWidget] reload: failed with error Couldn’t communicate with a helper application.) From Xcode: default 11:19:45.639908+1000 chronod [com.mr-brightside.myParcel.ParcelWidget:ParcelWidget:medium:-7973698613864559631@321.0/148.0/20.2] reload: begin default 11:19:45.802217+1000 chronod [myParcel.ParcelWidget-A713984DD536] Session operation: getTimeline request. default 11:19:45.939728+1000 chronod [myParcel.ParcelWidget-A713984DD536] Session operation: getTimeline result. default 11:19:46.129838+1000 chronod [com.mr-brightside.myParcel.ParcelWidget:ParcelWidget] reload: succeeded with 1 entries default 11:19:46.131989+1000 chronod Task [84] [com.mr-brightside.myParcel.ParcelWidget:ParcelWidget:medium:-7973698613864559631@321.0/148.0/20.2] Completed Full logs are available in FB8122742

Yes, this is the same issue that is reported in multiple different threads. WidgetKit crashes when a widget is installed from a TestFlight build that was compiled with Xcode 12 beta 3.

Usually when you include a framework into a project it is embedded only by a single target (e.g. the main app) and then is used by different extensions as well. With app clips things are different, they are installed separately from other targets. Therefore, you need to have the “Embed & Sign” option to be enabled for all relevant 3rd party frameworks on the App Clip target settings page in Xcode.

If you check the NSItemProvider from PHPickerResult, you will see that it has "suggestedName" property. This will be your file name. I don't have any additional information about raw image data and creation date, sorry.

Ok, here is the solution to this problem. Make sure that you use Xcode 12 beta 4 and iOS 14 beta 4 on your devices. Make sure that you have placeholder(in:) implemented. Make sure that you don't have placeholder(with:) because that's what the previous beta of Xcode was suggesting with autocompletion and without that you won't get your placeholder working. I think this whole problem is caused by the WidgetKit methods getting renamed but that's another story. As per the release notes, you need to set "Dead Code Stripping" to NO in your extension target's build settings. This is only necessary for the extension's target. When uploading your archive to the App Store Connect, uncheck "Include bitcode for iOS content". Delete your old build from a device when installing a new beta. That should do the trick.

Same problem. Submitted a bug report (FB8889904)

I have the same problem. I believe it is a bug in iOS 15 beta 4 and macOS 12 beta 4. It happens only when a 3rd party app is built against the new iOS 15 / macOS 12 SDK. Full error message: <CKError 0x60000197dcb0: "Account Temporarily Unavailable" (36/1028); "Account temporarily unavailable due to bad or missing auth token">  Submitted a feedback: FB9411756

Please don't forget to create a new feedback. Apple needs to prioritize this bug.

Fixed in beta 5.

Same problem here. Looks like App Intents are a bit rough in beta 1.

Same issue in Xcode beta 4 :(

Same problem. Looks like a bug in the App Store Connect.

Ok, it looks like either Xcode 15 or the App Store Connect that is mistakenly marking AVFoundation framework as private. Hence the bug. After stripping AVFoundation from my project, I was able to avoid this error. Good luck if your 3rd party library is using it though. What is interesting is that if you check the main header for AVFoundation you will see similar files that are getting imported by the framework and then marked as private: #if __has_include(<AVFoundation/AVFCore.h>) #import <AVFoundation/AVFCore.h> #else #import <AVFCore/AVFCore.h> #endif #if __has_include(<AVFoundation/AVFAudio.h>) #import <AVFoundation/AVFAudio.h> #endif #if __has_include(<AVFoundation/AVFCapture.h>) #import <AVFoundation/AVFCapture.h> #else #import <AVFCapture/AVFCapture.h> #endif Submitted FB12425841

Fixed in Xcode 15 beta 3.

It is broken. Submitted FB12555541 one month ago, no response yet.