Same symptoms over here.
Map opens and closes 1 second later.
Zwift running on latest game version on Apple TV, latest TVOS.
Zwift Companion App running on latest app version (3.30) on iPad Air2, latest iPadOS (15.1).
One month, one app update and 322 posts as of this writing. Nonplussed.
Note: Map works fine on Android device, but that thing is puny and a horrible user experience.
2 Likes
Can i just add that trying to carry the yellow beacon and lead group rides without being able to message the group (because the companion app is not working) is very difficult.
I have tried running the game both on Apple TV and on Windows and get the same issues with the Companion App on my iPad, sometimes Map loads for a few seconds then returns to main CA screen, sometimes is hangs on load with the blue Z screen, sometimes hangs on load with just a white screen.
PLEASE PLEASE FIX. A
5 Likes
Hey ZWIFT, ANY UPDATES AT ALL? ANY COMMENTS FOR THE COMMUNITY ON THIS? ANYTHING? It has been a MONTH with crickets. Goodness.
6 Likes
The companion ap. issues are becoming quite a common topic of chat on zwift group rides now Iāve noticed.
2 Likes
Glad youāve noticedā¦ā¦ on all the group rides Iām going there is no chat because no one can access it on the app 
Zwift really could do with making a statement about it.
1 Like
This does not sound right since many people are on android phones or they use there keyboards on PC.
ā¦but then again on bigger group rides the chat is still broken by design (can only see messages from the leader and the nearest 100), isnāt it?
1 Like
I think itās a combination of the rider number and companion usage, on a ride with over 230 people there were possibly 30 to 40 messages in the hours, where usually itās a constant stream.
Can I suggest we all start writing negative reviews on the App Store for Zwift companion. Then Zwift and possibly Apple might do something about the app not being fit for purpose when used on an iPad.
3 Likes
Done that.
Donāt think Apple can or will do something about this. This is a Zwift problem, going on for a month. And they donāt care as long as people continue paying. Only way to get them to do something is CANCEL your subscribsion, but people āloveā Zwift so much, so they post their frustration on this forum instead. And Zwift donāt care, i guess even donāt read it.
Perhaps some of the āYouTube influencersā should get on the caseā¦ shame Zwift into fixing bugs
3 Likes
What amaz me is that they not done that already. GP Lama have regulary updates on all the new ā ā ā ā they introduce, not a word about one of the most usefull functions in the game been unusable for a month now.
This seem like a bug that only affect a particular group. Not all iOS devices are effected and therefore it is hard to solve if they canāt replicate the issue.
So It will help to give more specific information about the setup.
1 Like
Or even acknowledged it.
I can barely bring myself to say this, but even Garmin (notoriously bad customer support) have better customer support than this.
Iām growing in my suspicion that they (Zwift) have very little idea how to resolve this. Their silence at the moment speaks volumes.
People have obliged with requests from Zwift to explain their experiences. This has been done countless times.
Yet here we still are. A month on.
4 Likes
My understanding is that Apple will consult with developers, but that service is not free, and is not for debugging an app, but for how the app runs of the different Apple operating systems. Apple is not going to go through a developers code and find their mistake. The Companion runs, it just doesnāt do what it should. Apple isnāt going to be any help. They probably should rollback the app versions and rollback any changes on their server side. At least get to a point where the software is stable again, and then add features until it breaks. Preferably on a non-production server setup.
Since people that arenāt having the issue, if any, arenāt going to come to this thread and complain the apps work, we may never find out that the bug is up the appās butt.
EDIT: I did not experience these issues after I updated my iPad. I have been off the bike since October 28th, until recently, but that ride, everything worked. But, if it is a problem created/caused/enabled by macOS, and they have the membership for it, Apple would likely be able to look at the interaction between the OS and their app(s). It might take Apple a while to respond too. People think beta, and software testing in general is easy, but it can be a real PITA, and still, after months of testing, the product could fall flat on its face after being shipped because of an unknown problem, or a compatibility issue with something that they didnāt/couldnāt test for. But the anticipation is getting fever pitchā¦
And now I donāt remember when I updated my iPad. Itās been a bad month. Apple isnāt signing the older versions of ipadOS, so downgrading to an earlier version isnāt possible. DRAT!!!
1 Like
Gerrie,
From what I can tell there is a clear path to reproduce the bug:
The bug itself or at least the one first mentioned at the top of this thread is as follows āOpening up companion app once you are in a world ready to ride - the map view works while the circle around the player is completing and then once it is close to completing the app crashes out and returns to a view of not connected as if you are not activeā
The bug appears to be consistently reproducible (I have reproduced it on 2 different IPADās myself and confirmed on a 3rd IPAD how not to get it).
- IPAD 1 - IPAD PRO 12.9" - 15.1 IOS - Blows up every time on ZC
- IPAD 8th Gen Regular peanut - IOS 15.1 - Blows up every time on ZC
- IPAD 6th Gen Regular peanut - IOS 14.8.1 - WORKS every time on ZC
- IPHONE 10 - 15.1 - Generally works but frequently crash 75% way through an hour ride these days especially if I happen to change apps mid way to answer a text or something when using ZC.
My computer is Imac M1 2021 for Zwifting if it really matters I use BLE to connect to a Kickr Bike - From what I can tell its independent of the Zwift Computer used it is all about the delta from 14.8 to 15.1 the new OS in causing the issue. The only thing on my Imac is Zwift it is a single use machine that only runs Zwift as I have resorted to eliminating every other variable in order to reduce issues. So my entire ecosystem is not only Apple but also current gen apple (no potatoes / antiquated versions). Happy to share actual system specs if we really need to get to that level.
The fun thing is there is a 2nd Bug as well which I have also been able to reproduce fairly easily which occasionally rears its ugly head on this thread and that bug is the Blue Screen and not able to go into ZC. All I have to do is leave my house and find myself using just cell service for ZC as in try login while I am out doing errands and sure enough on my Iphone 15.1 it hangs . My assumption as the workarounds others are suggesting has to do with something to do with ZC not able to auto transition from Wifi to Cell or back or something but for me the only implication is I wont be giving ride onās to my friends when I am not trying to ride or at home .
Anyway, yes I do see in this thread that there have been a bit of confusion but from the start there was always a consistent theme anyone who upgraded to 15.1 was having this issue. Since I now only have 1 IPAD left in the house which is not 15.1 I have elected to not upgrade that to prove its is reproducible on 3 IPADās as opposed to 2 as at this point my experience using ZC is so miserable because it crashes I just need something to work.
Hope that clarifies.
11 Likes
Chapeau @S_ara_Lance_L.o.T
You hit the nail on the head.