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.
I realise itâs a holiday in the US today, but itâs a little surprising that weâve had no fixes for these new issues in the two weeks that this release has been out.
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.
