I did a workout today 5-feb, and the workout loaded just fine in the companion app. I didn’t change anything since my last workout a few days ago when I had these issues. Happy that it worked again for me.
Doing a workout now on AppleTV and Companion on IOS.
I still have the issue.
I am cycling and having the below screen. All recent updates installed.
One more observation: it randomly switches between running and cycling when the Companion app is restarted.
Does anybody know the official route to submitting a support ticket or something like that? I haven’t seen a single reply from Zwift to the various posts on this new “feature” around the forums — not even an acknowledgement that they’re aware of the issue and are planning to fix it in the next couple years, after they’ve added more socks and animals and stuff to the system. I tried to follow the link in the “No answers here? Contact our support team!” sticky post, but the website just hangs.
If the website is not working for you, try emailing support@zwift.com
Or try a different browser
I don’t think that email address has worked for initially logging bugs for some time.
1 Like
I also had this same problem today (companion app showed up blank during the workout, didn’t show the workout details at all).
My setup: Zwift on iPad Pro, updated to new version 1.33.2. Companion app on iPhone running latest iPhone CA build available to me: 3.43.0.
Edit: This was my first workout after downloading 1.33.2, I did a few workouts on 1.33.0 and didn’t have this issue.
I did a workout Saturday at home, my companion app worked fine and showed the workout/intervals. I did a workout at the office today and only the white ZC screen worked. The dark workout screen never actualized, but I did see comments from the other people in my “event.” I did notice that the MAP screen shows up first and then I have to click the Dashboard button in order to get to that screen. Whereas before if you loaded a workout via Zwift on the iPad/computer with the ZC open, when it connected to the phone it would automatically go to the dark workout dashboard screen.
I think this is still and issue Zwift is working out but we’re still all left in the dark about it.
I just noticed a new companion app version show up in the apple store - version 4.32.2 (says 6hrs ago). Says it fixed a bug when expanding event details while the screen was still loading, and cat enforcement icons being in the wrong categories, wonder if the first fix is related to this or not. Will try again tomorrow.
Thanks for the heads up on that, @SeattleSauve. I already did my day’s workout earlier today, when the ZCA workout page still wasn’t working on my iPad. But after reading your post I updated both my iPad & iPhone to the newly-released v3.43.2 universal ZCA app. Also saw that a new Zwift v1.33.3 was released for the Apple TV yesterday, so also updated that. Fired everything up, started a workout, and after force closing and restarting ZCA on my iPhone and iPad 4 times each, the workout page worked as normal 6 times and gave me the mixed up display twice. That’s better than 50%, so I guess as far as Zwift software goes that should be considered a success.
1 Like
Yesterday evening I did a workout and I was back again with a workout screen in the companion app that didn’t work. During the workout I closed the companion app and restarted it. After that the workout screen worked again. Only to notice that I have now a white progress bar in the top. I believe I had previously a graph presenting the intervals with the progress there.
Hi Roel, click on the bar and it will expand to graph.
I tested today after updating AppleTV and Copmanion on iOS. Unfortunately the issue remains.
2 Likes
Ya, so I guess I was wrong…did a workout today and the ZCA workout page on my iPhone was again all hosed up. Tried force closing and re-starting a couple times and it was the same each time, so I just gave up on the app.
Thanks for this excellent tip!
My workout loaded just as per normal in the companion app. It seems quite random to me…
Yup, WKO tab has not worked for me in meetups on my droid for over a year. Others have complained about this but Zwift have done nothing, so I borrowed an iPhone and have been running the app on that. Now wko tab does not work in meetups on the iphone either.
Is Zwift bringing out their own smartphone? 
Below is the answer I received from Zwift support. Not tested yet.
“This is a common issue when switching between running and riding on Zwift. You may need to remove the companion app, reboot the device and then reinstall the companion app in order to resolve this issue.”
I’ve never done a single running workout on Zwift, so this doesn’t apply, at least in my case. And, regardless, I’ve already gone through the uninstall / restart / re-install dance on my my devices. I’ve gone from the workout page working every single time in the past year on the ATV / iPhone / iPad setup I use to effectively never (with the exception of a couple seemingly random times) working at all in the last few weeks. Not a single hardware change to my setup, and the behavior started at the same exact time on both the devices on which I use Companion, after updating Companion on both (and Zwift on my ATV), so it’s obviously a software side issue.
Gaging from the utter lack if engagement on this from Zwift — I haven’t seen a single reply from them — I suppose this will just be another deprecation of core functionality that will go completely ignored and unaddressed for years.
4 Likes
Tested today the reinstal proposed by Zwift. It is not solving the issue 
Same issue for me in companion app, was working when the game client was 1.33.0 now on the latest game client its messed up.
Same issue for me this morning. I’ve never done a running workout (in Zwift) and I’ve never connected a running device. My workout was imported via TrainingPeaks connection. This was my first workout in Zwift, so I wasn’t sure what was normal, but it certainly didn’t feel right to see running pace as the metric.
Same issue for me. Companion and main Zwift app up to date. Never done a single run ever. Clearly a bug - await the fix from Zwift…