All I can suggest is just have zwift running on your iPad and nothing else. Therefore giving the iPad the least amount to do as possible. Maybe that might help…?
Yet another crash tonight. Argh! Hope a fix come zoon!
Ios 16.6 on iPad Pro…same story as many posters - has been rock solid for years and now I get 3 or more drops in an hour of riding which require logging in again. The distance ridden counter reflects cumumlative kilometerage but the distance to ride resets to the full distance for the selected route. When I save the feed to Strava only captures distance ridden to the first glitch, whereas on the Zwift companion app I csn see the total distance ridden.
I wish I knew what I did to fix it after it crashed on every ride for around 2 weeks. It just seems to have fixed itself, which is weird as heck. Sorry so many are having problems, and maybe mine will crash again before it’s patched. Very frustrating to be sure…
Just found out from an Ambassador that I’m not alone with this issue. It has happened to me 4 times over the last 2 weeks – everytime while I’m in the middle of a planned workout. It happens at various times (6 minutes in, 18 minutes in, and today almost 49 minutes into a 1:06 workout!). As stated already here, it allows you to continue in the world you were in, with the elapsed time, but the workout starts over from the beginning and you don’t get credit for finishing the route. iPad (5th Gen) running 1.46.0. Oddly today I got credit for both the aborted ride and the completion of the ride (with the total time), so it looks like I did 2 rides, one for 48:56 and one for 1:08:13.
I’ve had the exact same happen to me. Not every ride but enough to be quite annoying.
And everyone is up to date on iOS? Mine crashed for a while, and somehow it stopped. Racking my brain to try to remember what I did before it stopped.
Has anyone else had that happen?
The iPad would go back to the first screen, and eventually progress back to the ‘in game ride’ normal screen.
im having the same crashing issues. totally kills me. it seems to happen in the last 10 minutes of completing a work out. same equipment in the same location for 5+ years
as you’ve identified the root cause, could you let us know whether this is related to a certain route/map for example?
I’m just looking for a workaround for my training later today…
I have done the delete and redownload (in case something went wrong during the upgrade process) and was hoping for a positive outcome. Not sure if patch will come through before I actually ride tomorrow morning.
I am also having this problem. Zwift do you have a fix coming soon?
Everyone in this thread - please note that Zwift version 1.47.2 is a patch that addresses this crash. Please update from the App Store at your earliest convenience.
4 Likes
Excellent news! Thanks for the help here @shooj . I’ll test during my rides this week and revert with any issues.
Just out of interest @shooj , what’s the definition of a ‘low memory’ device? The wife has got about 8gb free…
@Neil_Allonby
It’s important to distinguish between “memory” and “storage.” When we say “low memory,” we’re talking about devices with 4GB or less of RAM installed, not how much free storage space is left.
Apple likes to hide information about RAM in their devices. It would help us if you’d tell us the specific model number of iPad. Here’s how to look that up. You can search for the model number on other sites like everymac.com that will tell you how much RAM is installed in that tablet.
Model number is A1822, seems it only has 2 GB of RAM, that doesn’t seem a lot to me… 
No, it is not a lot. But Zwift was still working fine until a recent update. The patch put into place this past Tuesday seems to be working OK so far (fingers crossed).
2 Likes
@shooj still crashing, even after the 1.47.2 patch. Please have the developers keep working on it.
1 Like
I’ve passed along your comment.
Thanks. For what it’s worth, I was on Makuri today, which does seem to be the biggest ‘memory hog’ of all the worlds, so that may not have helped. Either way, still a crash that, IMO, should not be happening. Also, thinking back about the crashing, it is clear to me that this started with the introduction of the holo-replays. I wasn’t getting crashes at the time, but there were definitely more ‘glitchy’ graphics. And with each iteration since things have gotten a bit worse, until the recent updates where the actual crashes have started. It doesn’t even seem to matter that I have turned off all of the holo-replay stuff, as it still seems to be doing something in the background, even if I am not visually seeing anything in-game.
I do realize that my iPad is not new anymore, and that the 2G of RAM it has is not much, but it nice if I don’t have to get a new device. I know a lot of other users have had their machines deprecated over the years, so if a 2 GB iPad will no longer work with Zwift, I guess that’s the way it is, but I also think that things like this need to be published ahead of time.
2 Likes