I'm also seeing the same, now on the RC build. This is on a new app and my first time developing for watchOS, so I thought it was just something I was doing wrong - but after trying it out on a watchOS 9 watch - everything works perfectly fine. On watchOS 10 RC + built with Xcode 15 RC my app gets authorizedWhenInUse when I call CLLocationManager.authorizationStatus, so I then proceed to request location, where I then get denied with Error Domain=kCLErrorDomain Code=1 "(null)"
I've even tried using the new way to fetch location using async/await (CLLocationUpdate.liveUpdates()), but seems to be the same issue, just in that case the task never completes or fails, I just never get a location. iOS app works fine on iOS 16/17. Watch app works on watchOS 9.
Anyone find any workarounds? I was excited to launch my first watchOS app at the watchOS 10 launch, but this bug has put a damper on things, and my app doesn't really work without current location. And I can't build with prior Xcode versions as I'm using watchOS 10 specific features...