Some time in the past two days or so, I lost the ability to use CityStrides on my phone (Pixel 8, Android 16). I’ve tried Opera, Chrome, and Firefox, cleared all caches, applied all updates, started in safe mode etc, and it still just freezes and then crashes the browser tab if I try to zoom in or navigate around a map, and is extremely slow on some of the other text based pages. I also deleted my last two walks on 3/31, the last day I am sure it worked on my phone, just in case either of those had corrupted data.
I can view and interact with everything on CityStrides seemingly normally on a laptop or tablet, so this seems to be my phone. But since all other sites and apps are fine and CityStrides was, as well, until I tried to use it today, I can’t figure out what’s going on.
Is there anything that’s changed in the past couple of days on your end that could cause this?
Same here with Pixel 7 and Android 16, Firefox and Chrome.
Text pages like ‘Profile’ do work, although a little slow. Any page which shows the map or parts of it is exremely slow, hangs and sometimes even crashes the browser.
Problem started sometimes Thursday evening (Central European time). Since every hint might be helpful: there was an effect for like 1-2 weeks, that on the LifeMap a recent route was only shown when I zoomed out (scale 1km or more). It needed several hours before I could also see the route when zoomed in. And that even when there was no delay for the LifeMap displayed on the status page.
Since this is my first forum posting I would also like to take the chance for a big, big thank you to James for the idea and for running this great site. This is exactly what I was looking for for decades to get my ass out of the house more often…
I can confirm I am having the same issues with a Pixel 8, including the behavior related to the zoomed in LifeMap. The LifeMap has had this issue in the past, but I assumed something with the new processing was causing this.
The main thing that comes to mind around this timeline is the latest Mapbox GL JS update.
I just released a version of the site that downgrades this back to the previous version. Refresh your browser tabs & let me know if things are working again.
@mark.darlington your comment is very recent - you might be using the downgraded version already (unless you’re also referring to site use yesterday & earlier today)
The LifeMap zoom issue is completely separate.
There’s caching in play, so if the version of your LifeMap was viewed/cached without the activity present then it’ll take some time for it to draw the version with the activity present.
I’d have expected the cache to be ~5 minutes, as it’s set on the server. I forgot about the extra cache service which appears to hold it for 4 hours. I’ll have to look into that - on the one hand that saves me money on bandwidth costs, and on the other hand a 4 hour bad cache is rough. Edit: I was able to reset the cache down to 5 minutes
@jameschevalier That seemed to do it. Opera started working right away, Firefox required a reload, and Chrome needed a cache clear/sign in, but now all three browsers are working as expected. (I can also zoom in/out move around the LifeMap like normal.) Thanks so much!
It’s actually really irritating that this resolved the issue, because I’m going to need to upgrade my Mapbox GL JS version. I can’t sit on a specific version.
Can you (whoever’s reading along) visit this page and let me know if it’s also crashing?
I’ll have to look into that - on the one hand that saves me money on bandwidth costs, and on the other hand a 4 hour bad cache is rough.