-
-
Notifications
You must be signed in to change notification settings - Fork 358
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App crashes devices with an Adreno 330 GPU -> use v58.2 #5954
Comments
There was a big change to different rendering library (from Tangram-ES in While full trace is not exactly the same, that (There was also a different global crash in 59.0 and 59.1, but that one hopefully should've be fixed - see #5850) |
Given that maplibre/maplibre-native#2206 is open for some time you may want to switch to older version such as StreetComplete 58.2 which still used Tangram as a workaround. |
Fwiw, for me if GPS location is off the world map is displayed, then tapping the + button makes the app crash. If GPS location is on then the app crashes immediately apparently when it tries to zoom in to location, same as #5920 Seeing the devices list from maplibre/maplibre-native#2206 (comment) the number of possibly affected devices is quite large; specifically because SC is also targeted at OSM new contributors and now with the latest update and F-Droid displaying only the last three versions the 58.2 version isn't even easily available from the repo to install, this and how to install v58.2 (enabling Archive once and after disable again) needs to be mentioned in the app description or some prominent place. |
Makes sense. Although of course it would be ideal if the Maplibre issue maplibre/maplibre-native#2206 would get fixed in recent future. Give it a like 👍 there if you're affected / would like to see that fixed - currently it seems only two people are interested in solving that, so it's probably not deemed too urgent. Also, if you can provide more information that might help it fix it, please do mention it there (like that info that it only seems crashes when zooming, not when image is static - if I understood that correctly @erAck ? Also, can you manually zoom/pan the image with GPS off, or does it also crash?) |
For those making it here: Old StreetComplete 58.2 (pre-MapLibre, i.e. last version without crashes on I don't know if downgrades are possible; or if one has to uninstall old version (which would lose all the unsolved quests / settings / quest presets!) and install new one 🤷♂️ If one can still ocassionally open the app (e.g. with GPS disabled or via activity launcher to open Settings directly) they might be able to |
and more importantly, solved not uploaded ones |
Uploading pending changes that I did with 58.2 (I was in a similar situation as Izzy) still worked for me if GPS location was off and thus the map needn't update. And no, downgrading is not supported (in F-Droid), one has to deinstall and install new from the Archive repo (or directly downloaded as mentioned by mnails). |
My policy is to close issues caused by upstream issues that are not actionable for us. However, I'll pin this issue so users that encounter the same issue know what to do: Indeed, if your smartphone has an Adreno 3xx GPU (issue maplibre/maplibre-native#2206 only occurs for that GPU as far as we know), your only option as a user is at the moment to keep using v58.2. |
Thanks to all of you! Good to know it's not only a known issue, but even the culprit is clear. Will probably try my luck with backup/restore (as described with location off, or via the root-based backup/restore scripts of Adebar – hoping I can restore UserData from the current version to the older one. |
@westnordost and that's where I'd wish for Fastlane per-release changelogs. Not necessarily for each single release and each single change, but for (potentially) "breaking changes", as "early warnings". Had I known before there might be problems with Adreno 220 CPU, I probably first had tried to figure it I'm affected – and set the app to "never update" on the FP2 then. No complaints, just a thought. And that changelog would only be needed for Luckily, I was able to transfer app+data to a device not affected (if someone needs details / a step-by-step guide, I happily provide it; it will require both devices to be rooted, though). My FP2 is long EOL (I had planned to replace it last year, but my new device is only to arrive in a couple of weeks from now), so I can then transfer SC again to the new device once it's set up. |
You had to backup/restore your data because you had local changes you didn't upload yet, I presume? Everything else would just be downloaded again after login, FYI. So, no need to backup anything. Oh right, actually, the quest presets and quest enablements/disablements/order would also be lost on a complete new install. (A Fairphone end of life? How, though?) |
https://www.fairphone.com/en/2023/01/09/an-update-on-fairphone-2/ |
No, I've kept the auto-upload active. It's rather the configuration and presets. And, in my case, the transfer to another device for verification 😉 @HolgerJeromin your link gives me a 404 (not available in Dutch, but English works) – but yes, that too. The linked page says "the device will start lagging behind in terms of security updates" (I'm using LineageOS, so that's a different issue) – but for me it's lagging in general meanwhile, especially when it comes to larger Flutter apps (Flutter, React, Expo all are quite heavy as they have to bring their entire environment (native libs) along). The FP2 is 32bit only, and the hardware would be considered "low end" today – something not considered by all development teams. SC was still running fine on it, though. OsmAnd takes ages to even start up. Installing new apps often fails, sometimes the device is acting up (WiFi dropping, or suddenly the battery lasting for max 5h as it did the past few days here but seems to have resolved itself, now saying "2d left" again – 1.5d was the average)… Almost 10 years is a good time. Once having moved to a new device, the FP2 won't be thrown away though, it will instead become a third life (this was already its second life, being assembled from 4 different sources thanks to its modularity – the replacement will be even more modular, a SHIFTphone8); test device or "smart display", or something entirely else, not sure yet but I will find something. |
I just tried backing up the data of the new version on an affected device with oandbackup and restoring the data after installing the old version. It doesn't work out of the box, I got:
But getting |
The app crashes at start, I ended up wiping app data. |
I'm using SC for years now and am happy with it. However, having returned from a 3-week vacation this weekend and applying the latest update, the app crashes on start. Today a new release popped in and I was hopeful – however, same situation: app crashes on start. Performed a backup (using root powers) transferring app and data to a different device: no issues there.
Device where it crashes: Fairphone 2 running Android 11 (LineageOS)
Device without problems: SHIFT6mq running Android 10 (ShiftOS).
Took a logcat and grepped for streetcomplete, the relevant line seems to be:
More from the logcat
How to Reproduce
Just start the app. It opens, shows the initial screen, a spinner (updating details), and crashes.
Expected Behavior
Does not crash
Versions affected
SC 59.1 and 59.2 (maybe 59.0 as well, I had skipped that as I was abroad). IIRC I last used 58.2 successfully.
Android 11/LOS only. As the device acts up already for a while, I cannot entirely rule out some issues with the device itself, though other apps still work fine. Could probably be some edge case, but if someone has a clue that would be nice.
The text was updated successfully, but these errors were encountered: