Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Standalone watchOS apps support #628

Closed
2 of 4 tasks
kwridan opened this issue Nov 6, 2019 · 5 comments
Closed
2 of 4 tasks

Standalone watchOS apps support #628

kwridan opened this issue Nov 6, 2019 · 5 comments
Labels
type:enhancement New feature or request

Comments

@kwridan
Copy link
Collaborator

kwridan commented Nov 6, 2019 •
edited

Overview

#623 adds initial support for watchOS platform targets to Tuist. In effort to incrementally add the necessary features this issue will list out the remaining items needed.

Requirements
@pepicrft
Copy link
Contributor

pepicrft commented Nov 7, 2019

Thanks for opening this up @kwridan :)

kwridan added a commit to bloomberg/tuist that referenced this issue Dec 6, 2019
@kwridan
Support generating info.plist for Watch Apps & Extensions
fa0b5a2 
Part of: tuist#628

- Added watchOS App / Extension defaults to the info plist content provider
- Watch apps reference their host applications bundle identifier in the info plist `WKCompanionAppBundleIdentifier` key
- Watch app extensions reference their host watch apps bundle identifier in the info plist `NSExtension.NSExtensionAttributes.WKAppBundleIdentifier`
- As such the parent project is now used to perform lookups for those hosts to extract their bundle identifiers
- Updated fixture to leverage generated info.plist files

Test Plan:

- run `tuist generate` within `fixtures/ios_app_with_watchapp2`
- Verify the info.plist files generated in `Derrived/InfoPlists` matche the ones created by Xcode
  (They were previously checked in under `Support`)
@kwridan kwridan mentioned this issue Dec 6, 2019
Merged
5 tasks
kwridan added a commit to bloomberg/tuist that referenced this issue Dec 13, 2019
@kwridan
Support generating info.plist for Watch Apps & Extensions
10754e1 
Part of: tuist#628

- Added watchOS App / Extension defaults to the info plist content provider
- Watch apps reference their host applications bundle identifier in the info plist `WKCompanionAppBundleIdentifier` key
- Watch app extensions reference their host watch apps bundle identifier in the info plist `NSExtension.NSExtensionAttributes.WKAppBundleIdentifier`
- As such the parent project is now used to perform lookups for those hosts to extract their bundle identifiers
- Updated fixture to leverage generated info.plist files

Test Plan:

- run `tuist generate` within `fixtures/ios_app_with_watchapp2`
- Verify the info.plist files generated in `Derrived/InfoPlists` matche the ones created by Xcode
  (They were previously checked in under `Support`)
kwridan added a commit that referenced this issue Dec 15, 2019
@kwridan
Support generating info.plist for Watch Apps & Extensions (#756)
de14ceb 
Part of: #628

- Added watchOS App / Extension defaults to the info plist content provider
- Watch apps reference their host applications bundle identifier in the info plist `WKCompanionAppBundleIdentifier` key
- Watch app extensions reference their host watch apps bundle identifier in the info plist `NSExtension.NSExtensionAttributes.WKAppBundleIdentifier`
- As such the parent project is now used to perform lookups for those hosts to extract their bundle identifiers
- Updated fixture to leverage generated info.plist files

Test Plan:

- run `tuist generate` within `fixtures/ios_app_with_watchapp2`
- Verify the info.plist files generated in `Derrived/InfoPlists` matche the ones created by Xcode
  (They were previously checked in under `Support`)
@pontusm
Copy link

pontusm commented Oct 22, 2020

Any progress on this? For example, deployment target and device does not seem to support watchOS.

@kwridan
Copy link
Collaborator Author

kwridan commented Oct 22, 2020 •
edited

Hi @pontusm,

There's partial support - but some bits are still missing.

An example of what's supported can be seen in the following fixture:
https://github.com/tuist/tuist/tree/master/fixtures/ios_app_with_watchapp2

@pontusm
Copy link

pontusm commented Oct 22, 2020

That's great to hear. I managed to work around it by using xcconfig-files and specifying the deployment target there instead. Maybe that is the recommended way to handle build settings instead of relying on Tuist to implement support for everything?

@kwridan
Copy link
Collaborator Author

kwridan commented Aug 26, 2021

Maybe that is the recommended way to handle build settings instead of relying on Tuist to implement support for everything?

Sorry for the late reply 😞 - just spotted this.

Ya Tuist may not be able to support every configuration permutation out of the box but common things can be added as use cases arise for it. Using xcconfig files is quite common for this - glad you found a way to get it working 👍

@kwridan kwridan changed the title watchOS support Standalone watchOS apps support Aug 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type:enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pontusm @pepicrft @kwridan