I have exactly the same question, what is in 10.22, is it having stuff from 10.55 beta or not? And I have not seen that fixed map drawing issue in beta releases at all.
Looking at my last run very zoomed in it looks like it is not actually snapping to the roads, close to it, but I guess it's more of a coincidence/gps issue then anything else. Leaving post below, just in case it isn't and others see some strageness all of a sudden too.
It's like a mystery game. Now we begin solving the new mystery.
"Fixed a map drawing issue"? Is this the issue everyone has been having lately, with the lines being all over the place, and people think it's a "follow road" setting that was enabled?
I'm still on 10.52 (according to watch) but am seeing the 'snap to road' issue quite clearly now too... so much so that I have been googling how to disable this for the past 15 minutes before seeing the release of 10.20... backend issue? Going to download the fit from the watch to see if it is borken in there too, or that it is just backend (hope so.)
Anyone tested yet? I assume that no fixes with version above 10.20, are included. Did we have any betas between 10.00 and 10.20?
There were several betas with higher numbers being the last one 10.55 but I've stopped at 10.51 because it has (so far) the best accumulated ascent till now. I'm actually confused with this new firmware number being 10.20... I´m gonna stay where I'm until further comments in the forum.
How is 10.20 from the latest issues point of view? Total Ascent calculation accuracy on bike activity and battery life? 10.55 has bpoth issues. (10.52 did not have)
