Update : This also happens with the release version of Xcode 13.

Having contacted technical support, they have confirmed that it appears to be a regression / bug in iOS 15. I look forward to the Apple bug-fix soon, and in the meantime there is a workaround. The workaround is, as mentioned in similar questions on this forum, to add a view modifier, in my case to the Hstacks that contained my pickers. .compositingGroup() As my pickers were also part of a '.popover' view, I in addition had to add the view modifier to the frame used in the popover view. So in my case it needed adding to both views (Hstack and popover).

Examined the package contents of the archiving, and can see that there are two copies of the extension, one in the Plugins directory and one in the level above. So, the one that is outside the Plugins directory is the duplicate. From the Xcode menu Select Windows\Organiser Select the archive, and click to show in Finder Right click to show the package contents of the .xcarchive file In Products\Applications find the .app file Right click on the .app file to show the package contents Examine the Plugins directory for the widget extension Examine sub-directories and higher level directories to find the duplicate widget extension What I still need to determine is what are the commands or build settings that created it, how to change them and how to correctly change the set up so that the incorrect duplicate is not recreated in a future build.

Yes, I have been experiencing this over the past few hours. For me it has been sporadic, as often it is failing with this error message displayed, however occasionally it has passed this point and moved on to the subsequent steps in the validation.

There was an additional instruction in the App's Bundle Copy parameters, to copy the widget extension in to the bundle. So, not only was the widget extension being embedded, I was also separately copying it in to the App's bundle. Uncertain how and when I managed to add this instruction in to the Bundle copy parameters, however I have confirmed that removing the instruction has fixed the problem with the archive and it now passes the Xcode validation for upload to App Store.

Go to the 'Payments and Financial Reports' section for your account on App Store Connect (assuming that you are using App Store Connect to distribute your app). Find the relevant month(s) when your app was purchased. If your account has been paid there will be a 'Paid' mark next to a 'Transaction ID' for that month. Also, check your bank account that you have setup (in 'Agreements, Tax and Banking') to receive your payments.

In trying to resolve this issue, I had loaded the widget directly on to the iPad. One time I received an error notification that the Apple Springboard failed to launch. This new avenue of investigation led to the solution in my case. Deleted the app from the iPad Deleted the widgets for the app (as I had loaded them directly) Powered down and restarted the iPad Downloaded the app, using Xcode, to the iPad Apparently the Springboard cache had become corrupted or has lost synchronicity with the developing app, and reseting it sorted out the issue.

That is what getTimeline in the TimelineProvider is for, although setting up for a cycle time of 5 seconds might hit a limit on the widget. Widgets are meant to be lightweight information providers, to minimise the interaction with your main app, and save on the battery power. So the all details are prepared in advance and the widget views created. The sequence is then stashed away and triggered to display at the appropriate time. Minimal resource used to run the widget.

Reverting to iOS15.5 in the simulator does not help when trying to check the operation in iOS 16.0+. There are changes in 'Locale' that are deprecated in iOS16.0, and new features that are introduced in iOS 16.0. Being able to change the simulator's locale setting is required in these instances. I have raised a feedback with Apple, and await their response.