-
Notifications
You must be signed in to change notification settings - Fork 819
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disallow the "watchOS" supported destination for multiplatform apps #1470
Disallow the "watchOS" supported destination for multiplatform apps #1470
Conversation
This commit also fixes existing test cases.
Hi @yonaskolb, @bcardarella and @FelixLisczyk I'm aware that this fix uses a little different approach than what was suggested in the issue discussion. Could you take a look at the change and let me know what you think? Thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please also update https://github.com/yonaskolb/XcodeGen/blob/master/CHANGELOG.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
Please update CHANGELOG.md
@freddi-kit, @giginet |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thank you! 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! Thank @tatsuky!
This PR addresses #1463, where the "Embed Watch Content" build phase isn't automatically generated when a watchOS app is created using the
supportedDestinations
configuration.According to Apple's documentation:
Xcode 15.3 is also not capable of creating multiplatform apps that contain the watchOS supported destination. Such the option does not show up on the UI:
Provided Xcode doesn't support it now, I had XcodeGen error out when
supportedDestinations
for an application contains watchOS. I added a new validation error case because I think this is an exceptional case that needs a special consideration.We can continue to create a watchOS app as an independent target by using the
platform
configuration as before. This PR does not affect the configurations of non-application targets.Tests
You can use the following example specs to verify the changes.
A "success" case using
platform
An "error" case using
supportedDestinations