My iPhone kept doing the same whenever I tried to enter the event. I ended up riding the same route in Watopia. Tried next stage a couple of days later and same thing happened. Ended up using laptop.
Had this happen to me on Sat when using my iPad Mini 2nd Gen (fully up to date), I was utterly devastated when I crossed the line and the app crashed. Loaded straight back in and “continued ride” but it just logged it as a normal ride.
Emailed Zwift and go this reply “At this time, we’re aware of an issue where certain members who completed a Virtual L’Etape du Tour de France event didn’t receive the proper kit. While they may have noticed a new kit in their garage, it probably wasn’t the one they were expecting.”
My issue is I got no kit at all let alone “one you were not expecting” luckily I do have an Email saying I have unlocked the kit so hopefully it is logged “somewhere” that I finished it.
1 Like
Shuji,
Any update on the issues with Zwift crashing on iOS/iPads? I am signed up to do stage 2 at the weekend, but I am in two minds about whether to go for it if there is a high chance that Zwift crashes during or (even worse) at the end of the ride! Is there anything you or we can do to prevent this happening, or any update on the position? (NB - I have sent you my log files as requested showing 4 crashes on stage 1, but not heard anything back).
Thanks,
James
1 Like
@Jamie_Tebs_SWCC and all those who sent in logs:
Thank you for taking the time to help us get to the bottom of this. We’re still investigating, but I will say the majority of the logs sent in are from older iOS 12.4.x devices. There are a slim number of exceptions from iOS 13, Win10, and MacOS users.
The premise that @Stephen_Betley suggested is just one possibility, but one that has merit. On Zwift’s end, we throttle down frame rates to lower-spec devices (meaning those with less memory / graphics power).
If you have an alternate (non iOS) device with better graphics capability and more memory, running it might be the safest bet for events with thousands of other people in them.
Even if you’re running a top-notch spankin’ new device, please reboot your modem & Wifi router.
I say this because I ran several of the logs through zwiftalizer.com. This is a third party site that analyzes issues. On some logs (not all), I saw significant network disruptions, which means your computer’s connection to the Zwift server was interrupted. If the other avatars vanished and you were alone - this is a symptom of being disconnected from the game server. If that network disruption happens to occur at the end of your ride when you’re saving? That can result in a crash, or the ride not crediting correctly.
Not that it’s any consolation, but I saw weird behavior as soon as I logged in to my L’Etape ride. All three worlds showed 0 riders in them. 
No avatars nearby when I spawned in Watopia. Out of nowhere, other avatars started showing up, and the Riders Nearby list started filling. Halfway up Epic KOM, everyone else vanished again, but returned a minute later. I knew what these things meant, and I looked at my own log after the ride Sure enough - network disruption spikes at those points. First thing I did after that? Rebooted my modem & router.
3 Likes
Hi running the latest IOS 13 and still crashing. Connected to fiber no network disruptions.
1 Like
Why is zwift using 3rd party sites to debug its own game? you dont have your own rescources? Can you please start working on the basics and get Zwift out of its perpetual early access phase. Waiting for 5 years for some polish and qol updates with bugger all but silence.
4 Likes
Same happened to me. App stopped working after 20-30 minutes doing the TDF rides. I am using a gaming standard PC running Windows 10, so no lack of computing power. Yesterday I managed to rejoin the event, but lost the first half’s file. Today I was unable to rejoin after 30 minutes.
I convinced my IT Manager that zwift was good for my health and well-being while we are still in partial lockdown and he agreed to install it on work laptop :0)
Did discovery stage one last night with about 1,400 others and worked fine. Appreciate not solution for all but moving off older iPad mini 2 helped. Only thing it didn’t do was save in ride photo but I’ll take it as a win.
Will try etape again at weekend and hope that works.
Thanks. I may try running Zwift from another device and/or reducing the resolution in the settings for these events. Will also reboot the router but I didn’t note any specific network issues otherwise at that time and seems a bit of a coincidence that it crashed in the same place at the start of the ride (immediately on starting to move after the 3-2-1 countdown) on two different days.
I have a followup question for those who crashed when using a smartphone / tablet:
Were you tethered to a TV or a bigger monitor when you crashed?
No @shooj - standalone device connected to power and Bluetooth to Wattbike.
No, just using iPad Air via bluetooth
No! Just a plugged in (meaning: charging) iPad and later iPhone XR (on battery).
Yes my IPhone X running IOS 13.5.1 was attached via Apple connector via HDMI to TV. Everything has been fine since the weekend, the only difference has been number of participants in group rides. The events that crashed 2000+
No, just standalone.
Yes I was using IPhone 11 running ios 13.something and using HDMI cable plugged into TV. I wasn’t alone on the course in fact the screen froze with me in a Peloton. I re-entered and it’s resumed my ride but this time I was not in the event nor on the same bike and in a standard orange jersey. I still have some people around me and I completely the course but sadly no result and no badge and no kit. Please help. Also want to do stage 2 on the weekend. Have emailed log files on Sunday already and hoping I don’t have the same issues.
My iPad crashed on finish also. I ended up in a tree when I resumed the ride. No badge for the Mt Route.
Hi all - we’ve been investigating the iOS crashes all week, and have an update. First - thanks to all those that sent log files. Collectively, they gave us a good sampling of data to examine. What we found verified our working theories:
-
The iOS 12 devices that crashed consistently exhibited Out of Memory (OOM) crashes.
Short term (meaning for the L’Etape events over this weekend and next), the simplest workaround is to use a device with more RAM, such as a laptop, if you have one handy. -
We also saw evidence of network disruptions in some of the log files. For everyone (including those on fiber connections), we suggest you reboot your modem, followed by your WiFi prior to minimize a risk of WiFi flakiness.
This weekend’s L’Etape events will be in France, on the Casse-Pattes route. It’s a beautiful ride and we hope you’ll join us (please update your game app before you ride!!).
- Doing any upcoming L’Etape event will unlock the 2020 jersey.
- You will also get to keep the 2019 kit if you earned it last weekend.
- If you experienced a game crash during a L’Etape event: we are working on a way to award you the correct kit without you having to report the crash on this thread or by emailing support. Please give us until next week, and we’ll update this thread as we make progress. Thanks all for your patience.
I rode L’Etape on iOS twice today. At 8am and 12noon on both occasions they crashed on the finish line. An event I did in between finished and saved ok. I managed to save the routes but the dotty socks I unlocked in the 8am event and the kit has not reached my garage. Any chance these can be added?
I have sent the log files
Regards
Pauline
[Letape_crash]
just had a MacOS crash at end of L’Etape stage 2 lap one at the finish banner. its the same thing as happened with lamb chop race one on the start banner.
Latest Mac software. latest MBP 16".
[Letape_crash]