just to ruin most theories - i never press alt+F4 and i get this.
I sometimes use the menu and save buttion and still get it
I sometimes use the companion app to save and i get this.
Sometimes when i use the menu and save route i don’t get it, sometimes when i use the companion app i don’t get it.
I don’t think this is to do with what we’re doing. I’m sure this is dependent on the speed from where you are to zwift’s servers at the time you try and save.
Toronto, Ontario. I don’t know where their servers are, but assuming California at worst, I’m probably as close, net geographically speaking, as NYC. I doubt it’s geographical.
Think that theory might also have collapsed:
Bay Area, West coast, USA… I’ve been getting the (indefinite?) Save hang on all my Zwift rides regardless of time of day (and regardless of whether I grab save from the desktop or companion app, whether I change the name, select images, or whether I let Zwift spam the club I’m not really a member of).
Hi folks, just a quick update on this one: We’re working on a fix and are planning on rolling it out in the next game release.
In the meantime, many have reported that if the Save screen is stuck spinning, they can navigate up to the little “Back” arrow, select that, and then try ending the ride again which often succeeds.
Thanks for your patience as we worked through this one.
Haha - This issue was caused by an intermittent issue in our UI code resulting from an previous change, so it wasn’t related to network performance (although I appreciate you and others helping dig into that line of reasoning - it did seem correlated).
Is this still an active case? I am getting it happening all the time at the moment. Is it still being worked on? I am on1.48.0 (120544) and running on windows. In the UK.
Thanks Chris! I have done this and it certainly looks better. Talking with Zwift support about this at the moment, so hopefully we will get a proper fix!
when video screenshots were first introduced it was an issue then it seemed to resolve itself so maybe something has reverted back somewhere in the background that they need to fix again.
Seems like a few people are having this issue again.