I had this issue today, and in my case, it was a stupid user error. I was setting up a new product on a developer account other than my own. Bundle ID and everything was configured correctly, and I confirmed that the identifiers were created in the correct place. However, I forgot to create an App. I was in the habit of testing this out on my own account, and simply forgot this critical step on the new account. I'm sure it's not what all you lot are doing, but it's a reminder that you should at least check the status of the App in Apple Connect. If it does exist, make sure it's available. I.e, not removed.

Flatout, I can confirm that the issue returned in Watch OS7. I have been trying to get Apple's attention to fix it again, but no luck. I'll keep trying, but it's been radio silence from them.

Thanks for posting this Gaston, it really helped me out today.

We have the same issue, and have some pretty reasonable usage. I'd like to know what the threshold is.

Hey, I have a good update on this issue. I got some time with Apple Engineers during the WWDC labs, demoed this issue, and they have since patched their servers to stop it from happening. Been testing the past two weeks, and I'm happy to report that the problem no longer exists. Thanks Apple!

I would be very interested in know this too!

We see this pretty frequently. It will be working fine, then all of a sudden it stops. Sometimes it can be restored by using an app on the watch that requires the phone (the Camera Watch app for example), then trying to run another debug session.

This is continuing to be a problem for us, we are getting several support emails a day around this issue, and nothing has changed in our codebase around Apple Sign-in since December. This issue just started a couple of weeks back, around the time that watch OS 6.3.1 was released, and has continued to grow.One user actually contacted Apple Support and they directed them to unpair, and pair their watch again. This worked for them, and it's what we have been directing other users to do, with 100% success. However, people are reluctant to do this, and they think it's an issue with our software. We did get one user to confirm that it also happens with Yazio on their watch too. Our downloads and sessions have been dropping considerably, and we have been forced to explore options around not using Apple Sign-in on the Watch.Is anyone else experiencing something similar to this?Any help would be much appreciated.

We are seeing something similar. We can access data through the app, but containers I know was able to use yesterday (I have screenshots!) I can no longer access.

I managed to get a partial fix for this.Xcode automatically generated an Identifier for both the App and the Watchkit extension:com.[COMPANY].[PRODUCT].watchkitapp.watchkitextensionWhen I tracked that down in the developer portal I could edit the description to something more appropiate.I haven't worked out how to update the Icon yet, I suspect it has something to do with the Apple ID looking for metadata from the Watchkit Extension target, but the data seems to be store on the App target.