Hello Zwifters
Phased rollout of game version 1.105 begins today to Windows / macOS / Android devices.
Phased rollout to iOS / tvOS begins tomorrow.
Wahoo and Zwift have enabled the KICKR Bridge feature for KICKR CORE 2, allowing Zwifters to pair their Zwift Ride, Zwift Click 2, or heart rate monitor through the KICKR CORE 2 to improve Bluetooth connectivity and to work around the Apple TV Bluetooth connection limit. To enable this capability, update your KICKR CORE 2 to firmware version 2.54 or 3.54 (or newer) using the Wahoo app.
Fixed an issue where some ANT+ devices could have a blank name in the Pairing screen.
Fixed an issue with extra lanes in New York on Central Park roads; Scotty at NYC DOT corrected the issue.
For races with event cooldowns enabled, fixed an issue where race rank could be incorrectly positioned on the Zwifter’s avatar on some devices.
Running: Improved the appearance of time input fields in Public Profile settings.
In group events, if a Ride Leader or Ride Sweeper have unsupported characters or emojis in their name, their event chat messages in the HUD will be shown as sent by “Ride Leader” or “Ride Sweeper”.
Android: Improved Bluetooth connection reliability for Zwifters on Android 15 and newer.
On the home screen, you may see a gradient profile on route cards when hovered / focused. This feature will be rolled out slowly.
UPDATE January 14
We are pausing the phased release of v 1.105.0 due to an escaped issue that affected rider placings not showing in the Riders Nearby list during a handful of races.
We are temporarily rolling back to version 1.104.4 on PC and macOS as the latest version, and plan to resume 1.105 rollout this week.
UPDATE January 15 Zwift Game v1.105.2 is rolling out on macOS/Windows/Android. iOS / tvOS release will follow shortly pending App Store review. has begun phased rollout.
Fixed an issue that could prevent race placements from being visible during races.
UPDATE January 16
We’re preparing a 1.105.3 patch to solve an issue that affects runners.
We are temporarily rolling back PC / macOS users to 1.104.4 (again).
Rollout of 1.105.3 will begin as soon as possible.
We are temporarily rolling back Android to 1.105.2 for the same reason.
UPDATE January 20
Zwift Game v1.105.3 is rolling out on macOS/Windows/Android.
iOS / tvOS release will follow shortly pending App Store reviewhas begun.
Fixed an issue that could cause running pace settings (in My Profile) to save incorrectly after being updated.
UPDATE January 21
Phased rollout of v 1.105.3 is complete to all OS platforms.
Do you have questions or issues to report? Let us know below.
It’s come to our attention that race placings in the Riders Nearby list weren’t behaving as expected during some race events. We will resume rollout of version 1.105 this week after we’ve addressed that issue.
In the upper right of the screen when you’re riding, under the map, is the name of the course you’re riding, an elevation profile, distance left, & KOM finishes.
I’m using an iPad Pro running iOS.
It no longer displays my current course, just a short segment that changes every 2-3 miles.
I strongly prefer the old way and hope it changes back.
Hello! We’re in the process of rolling out v1.105.2, which addresses an issue that could prevent race placements from displaying during races starting on macOS, Windows, and Android. Please update when it’s available to you.
iOS and tvOS releases will follow shortly. We’ll update this thread when that is available.
Hi @Sam_Barr welcome to Zwift forums!
Shuji at Zwift HQ here. I looked at your server logs and have a likely suspect.
Did this happen on today’s ride? If yes, you logged in on your iPad a few hours before you logged in again on a Macbook, and both were logged in simultaneously. This causes many different weird symptoms, including this one.
If your iPad is your preferred device, we recommend you uninstall Zwift from the Macbook to reduce this risk to almost zero. The other thing you can do from your iPad is to force-close Zwift after you log out. Manually force-closing shuts down the app completely instead of leaving it running, which is what happens when you just swipe the app into the background.
I am riding the Richmond Rollercoaster route right now, clicked in from Tour de Zwift on home page. I have been receiving random XP bonuses mid kilometers - and they seem to be accelerating. First was 24, then 72, now I just saw 88.
I am not in workout mode, and I am receiving 20 XP at each kilometer. The power up bubble is not filling, so it doesn’t feel the like the randomly placed XP bonuses in the Watopia tour last year. I don’t have any cycling workouts syncing from an external device right now. (Unless Zwift is finally giving XP for runs and it is backfilling right now - though that would be unfortunate to get cycling XP for outside runs).
I also saw a banner when I entered the world that I unlocked the camo running outfit (I’m riding).
Today was supposed to be a super short ride, but now I’m wondering how much XP I can farm from this (I assume) bug. Alas, I just got a +16 at 13.4 km, so I can stop when I finish the route.
I recently updated to MacOS 26.2, and Zwift (version 1.104.4) just pinwheels now. Ive attempted to uninstall, reinstall from dmg found on zwift website, but same issue occurs, just stuck on “Login Successful” screen. My ipad is on ipadOS26.2 , and i was able to launch and ride on zwift fine thankfully as a backup.
Hey @_Optimistic_Prominen - we’re looking into these issues. I had a quick question, if you look in your garage do you actually have the “camo running outfit”?
@_Optimistic_Prominen - Your suspicion was right, you did catch us backfilling outdoor running activities. We didn’t intend on granting XP during the backfill, so consider this running XP a bonus. More to come on tracking your outdoor running activities in Zwift in the coming weeks!
