Zwift Crash "Apple" After screenshot [SOLVED]

Similar issues here, on a MacBook Pro (13-inch, 2020) with an external GPU (AMD Radeon RX 580) and macOS Monterey 12.6.1.

I had multiple crashes yesterday in Urukazi, and even on the home screen, which has not happened previously.

I have recently noticed some pink “flashing” in certain places of Makuri, such as the approach to the Castle KOM and in a few places of Neokyo. I have no idea if this is related.

I uploaded the logs to Zwiftalizer, but there was nothing special to be seen there; the frame rate was fine, I got Ultra settings with 1440p resolution and the CPU load wasn’t too high either. It’s just that the Zwift app suddenly closes when I make a screenshot (not every time, but too often…).

2 Likes

Those activity fit files can be saved with a few steps; there’s a website called fitfiletools.com which has a “fix corrupt timestamp” tool, using this plus re-assigning an accurate date and time with their “time adjuster” I was able to manually upload the partial rides to Strava.

2 Likes

Adding some specifics to assist Zwift team’s debugging

Monterey 12.6
Macbook Pro 2016, tons of ram and ssd space

iOS 15.6.1
iPhone 13 Pro, 274gb available

Companion current as of 11.09*. Can’t get the app version as there is now a forced update… (* edit: App store dates this new update 3.41.1 as released 11.09, but I had checked before my Zwift session and it was definitely not in the app store at that time, for me anyway)

Crash did /not/ occur at first manual screenshot, I had taken a few others in course of the ride prior.

Game app on the mac crashed immediately after pressing the camera button in Companion.

Companion app returned to its initial “home” screen

No “resume ride” in Companion or in Mac game app after rebooting

Probably worth a separate thread (i haven’t looked to see if there is one), but I have noticed Neokyo consistently going epileptic for several months now so it’s not just you… Have managed to get some sweet screenshots. Likely unrelated to these recent Companion-app camera crashes tho.

Hi @Ryan_Hicks_RO

Shuji at Zwift HQ here. I see you’re using a MacBookPro13,3 (2016 Macbook Pro) running macOS 12.0. That’s a very old version of OS Monterey, and operating systems that far out of date cause weird random issues.

Would you check if your laptop can update to a newer version of the OS? If you continue to have crashes - please contact Support so we can provide one-on-one assistance for your laptop specifically by checking system crash logs on your laptop.

2 Likes

I’m on Monterey 12.6 (21G115) according to the About this Mac screen. Looks like there is a 12.6.1 dot release (from earlier today) I have not done, so will try that and hope for more stability.

Hey everyone,

I split off your comments into this dedicated thread. Sorry for the out-of-sequence sloppiness that caused.

We are investigating this crash as a high priority, and I’ll update this thread as we make progress.

7 Likes

Crash while merrily taking screenshots in Urukazi. Details:

  • Apple TV4k (2020 edition) running up to date TV-OS
  • Zwift ATV App and Android Companion current versions (using Companion for game control)
  • approx 20.7km into the “Makuri 40” route (high complexity cavern with scaffolding - attached screenshots below)
  • re-entered app, received an “activity in progress” dialog with option to continue it - re-crashed when selecting
  • second app restart, continue with activity dialog worked
  • back in ride where I left off EXCEPT: “Makuri 40” progress bar reset, despite having 20.7km on the trip meter
  • continued riding - and riding…and riding
  • fourth time around “Mangrove Maze North” - yeah, I think I’m stuck in a loop - I should be back at the start pens by now it auto-routing was working.

I’m here to sweat so I did a full 41km despite being sure I wouldn’t check off the Makuri 40 badge - fun ride regardless. I am curious if I’d ridden another 20km, would the game have given the badge, despite not being where I was supposed to be?

Pre-crash screenshot followed by post-crash resume - note the progress bars.

Resulted in two saved activities, map plot same but second one showing full distance.

Also: Hi @BooX and @James_Zwift !!! Nice seeing you guys, despite being trapped in the Mangrove Maze!

2 Likes

Great meeting you too Otto :grinning: Sorry to hear about the crash issue, but at least you got some miles in ( and a great excuse to purchase a gamer laptop :smirk: )

BooX

Responding to myself, I’ve done a bit of debugging which might be interesting or useful for the developers @shooj :

  • If I hit the camera button while being in the main menu, it crashes every time. Every time. Maybe I should stop doing that… :wink:

  • If the app crashes while being in the main menu, when I restart the app and enter the pairing screen, it first shows it struggles with Bluetooth (some triangle above the BT symbol) and after a while this disappears.
    I manage to connect to the trainer, but it’s unable to use ANT+ (which is what I normally use for connecting). The trainer, cadence and HR monitor only shows up as BT in the pairing screen.
    After rebooting Zwift another time, however, I manage to connect the usual way through ANT+.

3 Likes

Having the same issue. MacOS Monterey 12.6 (is not “very old”!). Main crashes immediately when trying to take screenshot. Lost an hour ride.

:laughing: I have a quasi-gaming laptop! (Core i5-11300H, 16GB RAM, Nvidia RTX3050)

I think I’ll hook that up to the TV in my pain-cave for the remaining Urukazi rides, until we’re sure the bugs are worked out. :big_z:

Unrelated: +17°C here today (“normal” would be +6.3°C) and I got an actual outdoor ride in too - practically unheard of for November in Ottawa, Canada. It’s been a lot of riding today.

1 Like

Do the games automatic screenshots crash it, or just manually taking a screenshot crashes it?

Continuing my debugging:

  • Regardless of which route I choose and how far I ride, screenshot number 20 triggers the crash.
  • This coincides with the maximum numbers of screenshots Zwift has been able to show (historically). Whenever I’ve done 20 screenshots or more (manually or automatically), only the first 20 would be accessible when uploading the ride.

So, until this issue has been resolved, this workaround seems to work:

  • Never make screenshots in the main menu, only while riding.
  • Never do more than 19 screenshots. (remember to include a margin, for automatic screenshots on every banner…)
4 Likes

@anderfo
Nice detective work! :male_detective:

We noticed something similar and are tracing the code underlying that 20 screenshot issue.

Best suggestion at the moment for Zwift running on Apple OS platforms is don’t take manual screenshots using the Companion app.

5 Likes

This happened to me today during a group ride that I am back up lead for (Poursuite de la Lanterne Rouge). The ride starts at 7:00pm UTC. At 7:18, my system crashed although not precisely after a screenshot as I had taken several without incident. (Another rider had a system crash at the same time I did.) I was able to rejoin, then the rider leader also had a system crash about 7:28, unable to rejoin. The beacon fell on me, but of course no fence control. I DID take several screenshots after rejoining with no further crashes. Sure hope this is patched before next week’s ZRL races :grimacing:

Well look at that! Went to my camera roll and yep, it was screenshot #20 killed each of my rides too. (Don’t really need 20 screenshots that’s for sure but you know, new scenery and all…)

Question tho, I had this issue when running the /previous/ version of Companion as yesterday’s update wasn’t pushed through to my app store when I checked before my rides. Just to confirm, you all are on the latest Companion version (updated late yesterday/early-today-ish) and also having the crash?

3 Likes

Not the person you asked but I can confirm I was using the latest version of the Companion App when I crashed. (I updated before I started my Urukazi ride) I was so snap-happy I’m not surprised I ran into the 20 pic limit.

Kind of amazed we collectively (@anderfo specifically!) figured this one out so quickly.

2 Likes

I had three rides crash in Makuri.

However, for all 3 rides the 18th picture brought the system down. Poof! The iMac screen flashed red, then the desktop appeared.

Mac OS (Monterrey) & latest companion app.

1 Like