I have an iOS app which I'm trying to ship to the Mac App Store.
The app was created for iOS 7, but has been kept up to date. I mention it because it has an old project file.
I'm able to build and run the app on my Silicon Mac fine.
However, when I archive with target "My Mac (Designed for iPad)", I get an archive of type "iOS App Archive".
Here's what I've checked:
- Target is set to “My Mac (Designed for iPad)”
- “SUPPORTS_MACCATALYST” is set to “YES” on the main target and the extensions
- “MACOSX_DEPLOYMENT_TARGET” set to “14.6” on the main target and the extensions
- “Supported Platforms” is set to “iOS” except for Watch targets and targets which also run on watchOS.
- If I filter the build logs for "Catalyst" there are no results. If I filter them for "Mac" there are no relevant results.
- Clean build folder
- Delete derived data
- Restart Xcode
- Xcode Version 16.2 (16C5032a)
- macOS Version 15.2
Other notes:
- The app has a widget extension and an intents extension and two custom frameworks
- When I try and archive for Mac using Xcode Cloud, it runs for 90 minutes and then fails. I suspect it’s related to this issue but I’m not sure.
I’ve had issues like this solved with DTS before, but that isn’t allowed any more.
Any help would be greatly appreciated.
These Designed for iPad apps are iPad apps, so they show up in the iPhone and iPad Apps tap of the App Store.
To help put clarifications around these features, Running your iOS apps in macOS is the documentation around this Designed for iPad feature. The starting paragraph reads:
iOS Apps on Mac runs your unmodified iPhone and iPad apps on Apple silicon with no porting process. Your apps use the same frameworks and infrastructure that Mac Catalyst apps use to run, but without the need to recompile for the Mac platform.
While that uses Mac Catalyst as infrastructure hidden under the hood, it's not the same thing as deliberately building a Mac Catalyst app through a dedicated build destination. When you submit a Mac Catalyst app created with a dedicated build destination to the App Store, it's a separate build and separate submission so that you can manage the App Store details for macOS separate from your iOS app.
As to your next steps, I'd look at some of the destination options in your Xcode project to see if you can suss out why the Mac Catalyst destination isn't visible, but the Designed for iPad destination currently is.
— Ed Ford, DTS Engineer