Thanks Quinn - I'd like the user level version as both a developer and a user too. I've filed this in Feedback Assistant: FB12328461
siburb
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
This is still a problem in Xcode 15.0.1 (& the current 15.1 Beta), and it does look like an issue with the project template. @jclardy did it work going back to Xcode 14 to create the initial project, or did you give up on the stand alone watch app and produce one with the parent iOS app?
I'm seeing exactly the same symptoms when trying to create a stand alone watch app. No iOS stub target at all, and the watch app target has an identifier of just ".watchkitapp" even though I've been through the process multiple times, making sure I give a proper bundle identifier during creation.
It also doesn't set the relevant plist values for a stand alone watch app e.g. "App can run independently of companion iPhone app", or "App is available only on Apple Watch".
If I correct the bundle identifier, and try archiving, I just get an empty "generic" archive with no app in it.
Logged feedback #13265919
Create watch only app:
This is what you get:
@LiveQuartz Did you ever manage to answer this one?
I'm assuming we use the ".watchkitapp" version when it is a stand alone watch app - and could possibly then switch to the "com.myCompany.myApp" version in future if we wanted to add a parent iOS app?
@sneqqy did you ever find out how to do this?
So, you've released a stand alone watch app without a parent iOS app, and it still shows up in the iOS App Store?
There's another way that you could choose - I've used it in a project after I ruled out significantLocationChanges because it woke the app up too often, and even when there was no change in location.
Try region monitoring. Set a large region around the user, and have the system wake the app when the user leaves the region. When that happens, set another large region around their new location. With this method, you get to decide just how "significant" the location change needs to be, and you also prevent the unnecessary wake-ups caused by the standard "significantLocationChanges".