I might be wrong but I thought there were quite a few recent reports of the client not being able to find the PP to do the teleport. But it could just be an old issue that’s also been reported recentlt, I dunno.
I’d drop the “if no club selected” part. It should remember your last choice but if you do share to a specific club it won’t remember that selection for next time, it reverts back to the first club in the list.
Thanks. A little bit of communication goes a long way, it shouldn’t be up to mugs like me to summarise stuff. Once again I question the testing, because this is a long list of fairly big issues to release to the public in one go, and take a month to resolve.
People often complain about the slow progress on new feature work on Zwift, but there are a lot of regressions and new issues that can slip through the cracks particularly with the broad device/OS support matrix Zwift has. Fixes to these issues might also create more issues etc.
It’s good to see Zwift is on top of a lot of these, but it does seem the codebase is a bit fragile unfortunately. Personally - I’ve been lucky, these haven’t affected me, the only issue I had in the last release was the companion app entrypoint to makuri island is broken and cannot be selected on my iPhone (mentioned in another thread). No point in fixing that now because the event is almost over, but it spent the whole event as a dead entrypoint on my iPhone.