After rebuilding the gym area of the house we decided to install to new TVs connected to 2 different Apple TV in order to be able to run and bike at once or while doing one of the activities watching a movie on the one the other screen.
Unfortunately when we connect the Apple TV to the TV (we have 2 of the same model) the app is instantly crashing after starting (not even to the linking screen).
If we plug the same Apple TV to any other screen the app starts without problems.
I think that perhaps the quality input of the TVs doesn’t fit the requirements of ZWIFT app in Apple TV.
Any idea of which settings to apply to the TV. I have tried changing them without any luck.
We have 4 Apple TV in total in the house, we have tired all of them switching between different TVs in the house and the effect is always the same, on that model of tv the app crashes.
Wow. That sounds like a really weird problem, and probably difficult for Zwift to debug. Though you can of course log it with them to see if they’ve got any ideas.
If it was me, I think I’d be trying to see whether putting an HDMI switch box in between the Apple TV and the Sony TV helps.
I’ve had some troubles with Apple TV’s in the past so throwing down some thoughts:
If using older generation Apple TVs with lots of content / apps stored on them, Zwift might not have enough bandwidth to run.
2A. Could be the limited number of Bluetooth inputs on the Apple TV, yet when I ran into this issue, Zwift would simply stop reading an input, not completely crash. The two new Apple TV’s recently released (2021 HD and 4K) still only have 3 Bluetooth inputs, yet 1 is used for the remote.
2B. If your trainer has speed and cadence on two separate Bluetooth inputs, get an ANT+ bridge to combine these into 1 Bluetooth input. Just note the new 2021 Apple TV’s only have a USB-C input.
Internet bandwidth is too low. Could be that the WiFi signal is too low in your gym, or the network is being saturated by the dual streaming or other users
Make sure the Zwift app is up to date, the Apple TV system is updated
Thank you very much for your insights. Unfortunately, the problem seems to be a different one in this case.
I have in my house 4 Apple TVs, 1 is already 3 years old, another 2 are from the last year and the last one was purchased last week. I have tried exchanging them between screens, all of them work without any problem on the other 3 screens in the house but crashing on those 2 new screens.
2A. I don’t manage to get to the screen where the Bluetooth is an issue. Additionally when trying on the other screens there is no problem and I am able to Pair the devices.
2B. As in the case before, plugging the same Apple TV to another screen makes everything work flowless.
The internet bandwidth in the gym is the best in the whole house. In the gym, we have the “server” and the main switch. I have tested the quality in both Apple TVs and the results are very good (above 800 download and 200 uploads)
Everything is up to date.
I have even moved one of the “other” screens to the gym, unplugging the HDMI from the new ones and plugging to the old one (in the same place, same connection, same Apple TV) only different screen (also Sony) and different HDMI cable (hard to remove the cable from the TVs on the wall) and IT WORKS!. Plugging back to the new screens and the app crashes again.
It is CRAZY! Tomorrow a company specialized in such equipment is coming to my house to “play” with the new TV settings. I hope I will have good news soon.
“ FYI - we have also been working on a fix for a similar-seeming macOS crash and the patch for that is v 1.13.1 that’s releasing tonight on macOS only. Just want to be clear that 1.13.1 will not fix the AppleTV issues. We appreciate your patience!”
I have to switch OFF ATMOS in APPLE TV and the app doesn’t crash.
I was just replying to the suggestion that this issues has already been tackled in the last update with the application. Unfortunately it hasn’t and therefore UNLESS I keep the ATMOS OFF the application crashes.
That’s a workaround. I assumed that when it was identified that switching off Atmos solved the problem, then Zwift fixed the bug where seeinf Atmos made it crash.