See my comment above on how the issue was resolved for me. On top of that another suggestions from Apple on my Feedback Assistent ticket was related to changing some build settings, I didn't try these, but posting them here anyway as it may help someone else: "The real problem here is most likely related to auto-linking. Auto-linking is a feature where linker automatically resolves library dependencies. For Swift code you can opt-out of that using the SWIFT_MODULES_AUTOLINK build setting, or using CLANG_MODULES_AUTOLINK for C/Objective-C code. For Swift you can also try some more granular options such as SWIFT_SKIP_AUTOLINKING_ALL_FRAMEWORKS, SWIFT_SKIP_AUTOLINKING_FRAMEWORKS, SWIFT_SKIP_AUTOLINKING_LIBRARIES to control what is auto-linked. Once you disable auto-linking you’ll see a bunch of undefined symbols, and based on that you’ll need to determine which frameworks/libraries need to be explicitly linked (configured through build phases as explained in https://developer.apple.com/documentation/xcode/customizing-the-build-phases-of-a-target#Link-against-additional-frameworks-and-libraries )"

In our project we are getting the same error on our WatchKit app target when we're trying to Archive the project. We are not using the -ld_classic or -ld64 anywhere in our project. In fact the Other Linker Flags for the Apple Watch target is empty. Adding -Xlinker -dead_strip -Xlinker -allow_dead_duplicates to Other Linker Flags did not make a difference. The Assertion we're getting is exactly as per the above, including the line number. Assertion failed: (it != _dylibToOrdinal.end()), function dylibToOrdinal, file OutputFile.cpp, line 5196 @DTS Engineer Is there any news on this? Is there something else we can do to work around this and will it be something that will be resolved in future Xcode betas? Or is there something else I am missing?

For some people it might be worth checking your Package.resolved file to see whether it got corrupted or simply rolling it back to a previous version. Swift Package manager was acting up for me for one specific project. Wouldn't add new packages, would not resolve existing packages, etc. It worked fine for other projects. I then took a look at the Package.resolved file and there seemed to be a merge conflict that wasn't pointed out by the repository tools. SPM started working as expected after resolving the conflicts.

I am experiencing the same here. Have you been able to try it on a real device yet? (I haven't so far). I would think it is a bug. I could work around it for now by going into Settings > Privacy > Location Services on the simulator and then Authorize the app there. I have submitted a ticket in Feedback Assistent for this.

It seems to work for me, however I would like to show a certain screen when the app is opened through the itms-services://?action=purchaseIntent... URL. But when I tap the URL none of my App Delegate life cycle funcs are being called, except applicationWillResignActive, but can't read the information in the URL. Is there a way to read out the intent and productID when the app is being opened this way?

Make sure your app complies to all of the below for the Watch App target: Add the entitlement as per @BenKoning's message Add a NSMotionUsageDescription to the Info.plist Add the value underwater-depth to the WKBackgroundModes key in the Info.plist Once all done it should hopefully work: https://developer.apple.com/documentation/coremotion/accessing_submersion_data

So far I haven't other than installing Xcode 13 again.. Have you found anything yet?

Same issue here, can't download the crashes using Xcode 14.3