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…
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+.
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.
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.
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…)
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
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?
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.
My first few crashes were with the previous Companion app (without an Urukazi map) and yesterday’s debugging was with the latest version. Same issues with both. So maybe the Companion app version isn’t the main issue.
Is this 20 screenshots in a single ride? Or will 20 screen shots since the last update trigger it to crash? I am doing a long badge quest this Sunday and will cry if I lose the ride. I never take manual screenshots FWIW.
My crash was caused by manual screenshot #1 for me, from the Companion app. Assuming that the auto screenshot (which I never use) didn’t take 19 screenshots in the 45 minutes preceding that. Riding on Urakazi now. Won’t dare touch the screenshot button.
Rode for 90 minutes today on Makuri. Didn’t take any screenshots manually and no crashes. Don’t think it’s related to the quantity of screenshots or the auto screenshots.
I believe there is one at 18 minutes 11 or 12 seconds and then one at each notable event, these include ending a workout, beating a PB and that kind of thing. So you’d need to go through a lot of sprints or climbs to hit the limit if you’re not snapping manual ones every few minutes.
I have a quasi-gaming laptop! (Core i5-11300H, 16GB RAM, Nvidia RTX3050)
