Same here

Same issue as well.

Same

@rsebbe all my watchOS10 TestFlight users experienced the problem, so I assume that normal App Store users will have this problem. The global reset of location permissions doesn't feel like a solution as I assume it resets permissions for all apps? Can't see many users agreeing to that for a fix for one app. As I said previously, what worked for me was backing out the single app watch recommendation which I applied. After that it was working again for everyone. I appreciate this isn't a solution for all of us.

Could it be the forced unwrap locations.last!

I reverted the commit which turned my watch app into a single app and uploaded to TestFlight. Location services are working again.

I reverted the commit which turned my watch app into a single app and uploaded to TestFlight. Location services are working again.

Ok, I traced my issue back to when I took the Xcode recommended setting to upgrade my watch app into a single app, removing the extension. My TestFlight build prior to that works, this build doesn't. However, I can't figure out the problem with the single watch app, I have a hunch the location permission setting is referring to the old bundle id (extension).

Ok, I traced my issue back to when I took the Xcode recommended setting to upgrade my watch app into a single app, removing the extension. My TestFlight build prior to that works, this build doesn't. However, I can't figure out the problem with the single watch app, I have a hunch the location permission setting is referring to the old bundle id (extension).

I am also having the same issue and it seems to have stopped working when I started to transition my app to support iOS17 and WatchOS10. My TestFlight users running WatchOS10 are having the same problem.

Same problem here. Working fine until installed WatchOS10 beta.

Started working the next day 🤷‍♂️