This is specifically a 1.57.0 issue. Prior to this update (which my Mac received 1/23/24) I could use the Apple Watch Companion app + iPhone Companion for semi-reliable heart rate data. Today, having downgraded back to 1.56.0 (because they paused the rollout for trainer resistance issues) I connected it and it paired up immediately.
My theory is they are working on the new app and somehow broke support for the old version in this update. If any Zwift devs or community members can relay this to the team, please donât break support for the legacy Apple Watch HR system prior to releasing the updated system!
Edit: Iâll add some more info on 1.57.0: I could occasionally get the pairing screen to show âApple Watchâ under heart rate sources. But it would never show my actual heart rate, no matter how many times I tried restarting the app (phone, watch, or computer). Maybe thereâs a wider Bluetooth issue besides my theory stated above, that is also causing the trainer resistance issues.
In general, this seems weird that there are Erg issues with specific trainers, when none of the âfixesâ in 1.57 seemed on the face of it, to have anything to do with this.
What is going on, wife riding and it kicked her out of the game on Android tablet. Checked update, wouldnât let her ride until it updated,⌠I thought updates were supsended,⌠and she did NOT already have 1.57
Itâs just as likely that they made a number of intentional changes that werenât mentioned in the release notes, one or more of which might be faulty for some reason. Iâd prefer more verbose release notes, but I donât assume those omissions are a sign of a sad code base. They also have a spaghetti hardware device landscape theyâre dealing with which isnât their fault, itâs just part of the challenge. Ideally they would test every release with real rides, workouts, etc. on every popular trainer, HRM, power meter, treadmill, etc, and a wide variety of devices that include every conceivable phone, tablet, mac, PC, etc. with every supported OS version. That is a huge matrix for testing. Rapid roll-backs are a sign of maturity IMO.
I updated my ATV to 1.57.1 this morning, UK tilme. Youâll probably find it now if you check. It takes some time for Zwift to get it approved and published by Apple.
Yes, I assume they are. Someone on 1.56 will update to 1.57.1 and see no functional difference (presumably), but at least most people who arenât on Mac/Windows should be all on the same version.
He doesnât need the update, but he might as well put it on.
There is no such thing as accelerated levelling, only delayed. I have enough XPs to shoot straight to L250 but it will take a couple of months, thatâs definitely longer than a jiffy.
Besides, we do not get double XPs. We have already earned those extra XPs that get added towards the next levels. We only get them back at a slow rate.
Now we get slowed down even more? Good thing you had to roll back.