I managed to solve this issue as well now. I tried all the weird solutions listed in this thread but none of them worked. What did actually solve it in the end was to just charge the watch before attempting to do the update. I'm pretty sure the actual solution for all previous posts in this thread isn't the actual resets etc they've done, but just that they've had the watch in the charger during the procedure so the battery has eventually reached its 50% and therefore been able to start the update. The real bug here is the UX of the Watch app on the phone that doesn't tell you this but instead lets you think it's due to a network failure. @apple please update the UX in the watch app so we get a proper message about this, it would have saved myself and tons of other people around the world a lot of frustration. And again, for everyone struggling with this, just leave the watch on the charger for 1-2 hours to get it fully charged, and attempt the update again and it should work.

I get the same error. Same build required ios 9 in May, exact same code now require ios 11 in TestFlight. I’m not even sure I dare to release a build any longer since it says iOS 11. Will it require that os version in the production release as well or is it just TestFlight?

I called Apple developer support just now. They where very helpful and will look into this issue right away as soon as I've sent them some screenshots and screen recordings which I'll do later today. I'll also refer them to this support thread so they see that more people are having the same issue and not just me. I'll post back here as soon as I get more info from them.

I have the same problem, there's another forum thread about the issue here: https://developer.apple.com/forums/thread/687778

Same issue as this thread: https://developer.apple.com/forums/thread/687778

Same here, did a new build with bumped build number and uploaded it just now and it correctly shows as iOS 9 in TestFlight.

We're also having this issue. It seems to be the same bug as discussed in the Firebase Unity SDK issue tracker here: https://github.com/firebase/firebase-unity-sdk/issues/916

There's a workaround posted by the Firebase developers in their forum: https://github.com/firebase/firebase-unity-sdk/issues/974#issuecomment-2024127530 That fixes the issue for me.