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.

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

Add product type "WatchKit App Container" to ProjectDescription #4534

Closed
thebarndog opened this issue Jun 7, 2022 · 5 comments
Closed

Add product type "WatchKit App Container" to ProjectDescription #4534

thebarndog opened this issue Jun 7, 2022 · 5 comments
Assignees
Labels
bounty Resolving this issue is rewarded with a bounty: https://github.com/tuist/tuist/discussions/4982

Comments

@thebarndog
Copy link

Describe the bug and the expected behavior

When creating a standalone watch app, Xcode will generate 3 targets:

  • a WatchKit app container with the product type com.apple.product-type.application.watchapp2-container
  • a watch kit app with the product type com.apple.product-type.application.watchapp2
  • a watch kit extension with the product type com.apple.product-type.watchkit2-extension

ProjectDescription.Product needs an additional product type to represent watch kit container targets which is essentially an empty iOS target with corresponding product type com.apple.product-type.application.watchapp2-container.

As a side question, are there any tuist plugins that are able to generate a standalone watch app or watch targets in general? Something like that would be incredibly useful rather than the alternative which is having to know exactly what targets Xcode creates and how they're structured.

@thebarndog thebarndog changed the title Add product type "WatchKit App Container to ProjectDescription` Add product type "WatchKit App Container" to ProjectDescription Jun 7, 2022
@fortmarek
Copy link
Member

Hey @thebarndog 👋

That's a reasonable addition. Would you want to contribute to this?

that are able to generate a standalone watch app or watch targets in general?

I'm not aware of something like that being available. But you are more than welcome adding that by creating a template plugin (see documentation here)l. Depending on the template, you could then run tuist scaffold --template watch-target --name WatchName which would generate the files specified in the template.

@thebarndog
Copy link
Author

Yeah I can certainly take a crack at it. It might not be for a while but it's definitely something I'd love to see!

@danieleformichelli danieleformichelli added the bounty Resolving this issue is rewarded with a bounty: https://github.com/tuist/tuist/discussions/4982 label Jan 24, 2023
@github-actions
Copy link
Contributor

Hola 👋,

We want to inform you that the issue has been marked as stale. This means that there hasn't been any activity or updates on it for quite some time, and it's possible that it may no longer be relevant or actionable.
If you still believe that this issue is valid and requires attention, please provide an update or any additional information that can help us address it. Otherwise, we may consider closing it in the near future.
Thank you for your understanding.

@github-actions github-actions bot added the stale label Jul 19, 2023
@github-actions
Copy link
Contributor

Hola 👋,

We want to inform you that we have decided to close this stale issue as there hasn't been any activity or response regarding it after marking it as stale.

We understand that circumstances may have changed or priorities may have shifted, and that's completely understandable. If you still believe that this issue needs to be addressed, please feel free to reopen it and provide any necessary updates or additional information.

We appreciate your understanding and look forward to your continued contributions to the project.

Thank you.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 25, 2023
@thebarndog
Copy link
Author

@fortmarek now that standalone watch apps exist and "watch app + watch extension" have fallen by the wayside with Xcode 14+, does Tuist support this yet? And if not, would the approach you outline above, creating a template, be the recommended way to build it into the core functionality?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bounty Resolving this issue is rewarded with a bounty: https://github.com/tuist/tuist/discussions/4982
Projects
None yet
Development

No branches or pull requests

3 participants