I have posted so many bug reports to Apple over the years, many that were requested from me on these forums, and none have ever been resolved, most aren't even responded to, so I don't really want to keep doing that. This functionality I'm describing isn't documented anywhere, as are many of the other issues I post, whether it's a bug or a feature, I was hoping someone on this forum would have some insight or could direct me to the right place. Thanks

Thanks for confirming. I submitted a feature request, definitely a much needed feature for standalone Watch apps.

There was never any response to this. Any idea where I can get more information on how to handle this, it's not documented anywhere.

Thanks, we found the problem was with a property in the info.plist that didn't belong there.

FB13983855 I'm not sure if this is necessarily unexpected results, I just don't see any documentation on how to hide this feautre, and also how to respond to the action button press within an app.

When I click that link it says: "Sorry, you cannot view this page". Can you show me exactly what logs you need and how I'd get them from my devices? Thanks

Yes of course

Is there any fix coming for this or temporary workaround? We are currently not able to get it working no matter what we do and have been unable to work on our watch app all week.

No that doesn't work. I've also tried rebooting every device. Sometimes quitting Xcode and starting it again gets it working. But that only lasts a few launches and then it fails again. Once it fails at that point it where restarting Xcode doesn't fit it, it wont work for the rest of the day. I can't identify any reason why, but when I come back the next morning it usually works again, but then fails after I launch it a few times and then wont work again for the rest of the day.

FB11603770, thanks!

Yup. It sometimes works that if you restart Xcode it will work again for a couple launches, but always fails again. Then I go through restarting all my devices. Sometimes that gets it working, but at that point most of the time it never works again for the rest of the day and we have to stop working on our Watch app. I have found debugging on an Apple Watch to always be this buggy. I swear our Watch development cycles are probably weeks-months longer because of these issues.

Yes, everything is unlocked and connected. It's showing up paired in Xcode. Everything is set up correctly, this is 100% a bug in Xcode.

I'm on iOS 16 with watch OS 9 and am having this same issue. I updated to 14.0.1 and it didn't fix it. What can I try next? We've tried everything and are unable to get it running on any Watch.

Was considering that next but thought that was just for code level support so wasn't sure if they could help.

Any idea? Apple isn't helping me.