Post not yet marked as solved
You need to build a framework from the source code, starting from the Framework template in Xcode. Technote 2435 has the info you need.
Post not yet marked as solved
This is best handled by contacting Xcode Cloud support.
.handleInApp is only useful with specific intents. What do you expect to do with your app specifically in the background? Your intent extension is running as a background process, so you can perform work on behalf of your app in the background with this setup. You can also move your intent handling code to your main app entirely (eliminating the extension point) and handle the intent in the background that way, but before you do so, you should be clear on what work you expect to do in the background.
Post not yet marked as solved
Binary targets need to be declared as .binaryTarget, and need to be packaged as an XCFramework.
Further, the names of everything must be consistent, and it's not clear from this example if that's true. As stated in the referenced article:
Ensure that the name of the binary target in the package manifest matches the artifact’s module name.
Post not yet marked as solved
What is the binary file named?
Generally, the advice in the error message is accurate, and you can rearrange your target phases by dragging them around. In your screenshot, I don't see the right target phase types, as this looks like a screenshot of the app target and not the framework target's build phases. Check in your framework target's build phases instead.
Post not yet marked as solved
All of your points are correct. It's normal for extension targets to have more recent different deployment target when the extension point is new, providing benefits to customers on those newer version of iOS where the extension point is available. In time, those extension deployment version numbers will match the overall app deployment target as the minimum target of the app moves up over time.
Post not yet marked as solved
The information shown in the Xcode Organizer is collected by the system and delivered to you through the App Store. You can capture similar information with MetricKit; however, MetricKit provides this information for you to manage however you wish, including uploading the logs to a service that you control. Your implementation of MetricKit does not affect the information shown in the Xcode Organizer.
Post not yet marked as solved
Thank you for the bug report. This is a known issue, and is listed in the Xcode 14 Release Notes.
There isn't an API to add your own 3D features to the map, so we'd love to hear about your needs through Feedback Assistant.
Since you mention the London Eye specifically, iOS 16 brings the Detailed City Experience into apps using MapKit, which includes detailed 3D building geometries, such as the London Eye. London is supported, and the full list of locations is available on the Feature Availability page. To see this for yourself, you can take this sample code project and modify it to use London and the London Eye.
Post not yet marked as solved
Could you open an enhancement request with your needs? Even outside of Xcode Cloud, creating an XCFramework requires a script to do the final packaging of the different destinations into the final XCFramework package. Backing up a step in the process, I see your point about the archive actions in Xcode Cloud limiting you here, unless the XCFramework is for macOS.
Once you open the enhancement request, please post the FB number here.
Post not yet marked as solved
Please file a bug report through Feedback Assistant, including a sample project that imports your framework, and then post the FB number here.
Post not yet marked as solved
What specific iOS version are you trying to run in the simulator?
Post marked as Apple Recommended
Xcode 14 is required by macOS Ventura. See the Xcode 13.4.1 Release Notes:
Note: macOS Ventura 13 only supports Xcode 14 beta.
Post not yet marked as solved
There are some hints about makefiles in the Apple silicon documentation.
