I did a big ride to complete the 50k meters altitude challenge and noticed after it was completed that Zwift reverted back to the stats prior to the ride, and subsequent rides wont upload. Checking the activities folder I see one named inProgressActivity.fit with a time stamp matching the ride that first failed. Any way to get that one uploaded and get Zwift to record my ride progress again?
I found the log file and searched for the ERROR strings. Do these point to anissue?
[16:05:41] ERROR: Missing Vertex Shader asset data/shaders/Final/SSR.vsh
[16:05:41] ERROR: Missing Vertex Shader asset data/shaders/Final/innsbruckTerrainShader.vsh
[16:05:41] ERROR: Missing Vertex Shader asset data/shaders/Final/accessory_instanced.vsh
[16:05:41] ERROR: Missing Vertex Shader asset data/shaders/Final/RadialBlur.vsh
[16:05:42] ERROR: Missing Vertex Shader asset data/shaders/Final/moon.vsh
[16:05:42] ERROR: Could not load wad file: assets/Humans/Accessories/FacialHair/Beard.wad
[16:05:47] ERROR: Could not load wad file: assets/Humans/Runner/Runner.wad
[16:05:47] ERROR: Could not load wad file: assets/Humans/Runner/Runner_Textures.wad
[17:09:04] NETCLIENT:[ERROR] Error refreshing access token: [400] {“error”:“invalid_grant”,“error_description”:“Session not active”}
[17:09:25] NETCLIENT:[ERROR] Failed to fetch periodic info: [23] Could not acquire access token because credentials are missing
[17:10:25] NETCLIENT:[ERROR] Failed to fetch periodic info: [23] Could not acquire access token because credentials are missing
[17:11:25] NETCLIENT:[ERROR] Failed to fetch periodic info: [23] Could not acquire access token because credentials are missing
[17:12:25] NETCLIENT:[ERROR] Failed to fetch periodic info: [23] Could not acquire access token because credentials are missing
[17:13:25] NETCLIENT:[ERROR] Failed to fetch periodic info: [23] Could not acquire access token because credentials are missing
[17:14:25] NETCLIENT:[ERROR] Failed to fetch periodic info: [23] Could not acquire access token because credentials are missing
[17:15:26] NETCLIENT:[ERROR] Failed to fetch periodic info: [23] Could not acquire access token because credentials are missing
[17:16:26] NETCLIENT:[ERROR] Failed to fetch periodic info: [23] Could not acquire access token because credentials are missing
[17:17:26] NETCLIENT:[ERROR] Failed to fetch periodic info: [23] Could not acquire access token because credentials are missing
[17:18:26] NETCLIENT:[ERROR] Failed to fetch periodic info: [23] Could not acquire access token because credentials are missing
[17:19:26] NETCLIENT:[ERROR] Failed to fetch periodic info: [23] Could not acquire access token because credentials are missing
[17:20:26] NETCLIENT:[ERROR] Failed to fetch periodic info: [23] Could not acquire access token because credentials are missing
[17:21:26] NETCLIENT:[ERROR] Failed to fetch periodic info: [23] Could not acquire access token because credentials are missing
[17:22:26] NETCLIENT:[ERROR] Failed to fetch periodic info: [23] Could not acquire access token because credentials are missing
[17:23:26] NETCLIENT:[ERROR] Failed to fetch periodic info: [23] Could not acquire access token because credentials are missing
[17:24:26] NETCLIENT:[ERROR] Failed to fetch periodic info: [23] Could not acquire access token because credentials are missing
[17:25:27] NETCLIENT:[ERROR] Failed to fetch periodic info: [23] Could not acquire access token because credentials are missing
[17:26:27] NETCLIENT:[ERROR] Failed to fetch periodic info: [23] Could not acquire access token because credentials are missing
[17:27:27] NETCLIENT:[ERROR] Failed to fetch periodic info: [23] Could not acquire access token because credentials are missing
This issue popped up earlier this year for a few people and Zwift recommended a support ticket (see here). No solution was mentioned in forums but I’m picking its a connectivity issue in Zwift land somewhere tat it didnt recover from.
I’m a ride away from the 50k as well and last night I accidentally hit the trash can rather than save button and had a coronary until I realised it had a “are you really sure …” followup question, so totally get your anxiety around this level. Never seen the Zwift team load a users fit file after a problem but you can load into Strava (doesnt help you with the 50k achievement sorry).
Log a support ticket and ask them nicely to load the file fit file while they are at it. Good luck.
Thanks Dean. I’ve logged a support ticket and hopefully they can get Zwift working for me again. While waiting for support to respond, I tried again today with a couple of rides but none are uploading to Zwift. Connectivity looks fine and I see other riders no problems. Login is alway successful but rides no longer synch unfortunately.
While you are waiting for the Zwift team, you could install Zwift on another device and hook it up to your trainer (if you had a spare device). This would be very telling if the problem “followed” you.
Do you mind updating this thread when you get it working? Might be helpful for others that may encounter the problem in the future (being a bit of a techie, I’m also curious!).
I tried a quick ride on my iPad which didn’t upload, but then while googling issues I found that shorter test rides don’t show up as activities on Zwift, so my next test was a longer ride (20mins) using the PC where the issue occurred and the new activity shows up ok. The original failed ride has partial data when I see the activity in the Zwift companion app, but strangely doesn’t show the course and the (partial) distance and altitude aren’t added to my cumulative total so it must be corrupted.
Edit: Looking at the Zwift activities folder, I see there is a new inProgressActivity.fit file so maybe you have to ride long enough for the original corrupted inProgressActivity.fit file to be overwritten.
Edit2: Just tried a quick 10m test ride on the iPad before I have to go out and it shows up ok now too. Not sure if I was originally under some time limit constraint, or if it was the overwriting of the inProgressActivity file.
FYI - my shortest logged rides are approx 2.1km and/or ~6.5mins in duration with a 2.2km/9min43s last night.
Great that its working now. Doesnt explain the gremlin you originally encountered but the log indicates it was an issue on their side and unless you get a lot of these types of issues, I suspect it will be a one-off for you (looks like a security certificate glitch which blocked their servers from being able to see their data).
I think your assumption regarding the inProgressActivity is correct - my file from my group ride last night is still there though the timestamp shows it finishes exactly the same time the “ride event” finished and doesnt take into account the additional 5-10mins I continued to do afterwards. Zwift doesnt record “cool down” stats either (though it parses it all to Strava). We would have to exist/save to record that additional info.
I also started a ride while looking at the files but didnt spin the peddles - tried up to 6-10 min duration and it didnt record anything so suspect it is distance based before it over-writes.
1 Like
I suspect you are correct. I immediately restarted Zwift after the ride and noticed I had to provide my login details again, something I normally don’t have to do. Even transient internet disconnects don’t corrupt files like this I have noticed, and Zwift normally recovers from them without issue.
Zwift support came back to me with a stock answer “You’ll typically see a partial ride if you get disconnected from the Internet during a ride or crash” etc. They did mention an interesting point about short rides: “If a ride is less than 2 km, it won’t upload to Zwift or third-party sites : this was designed to prevent short test rides from clogging up activity feeds, while longer rides (over 2 km) should record normally.” That’s good to know.
1 Like
Took me a few days but I am finally back to where I was when the problem occurred. A bit of bonus pain.
1 Like