Crash on startup (v59.0-alpha1, Android 9, Moto X4) #5829
Comments
|
Do you have logs of the crash? |
westnordost
added
the
feedback required
|
I'll admit I'm not sure what to look for. This is the only Warning log in the app itself: Other than that, what's the best way to get crash logs? I assume this will happen again, and I'll try to get you that info. |
|
The app should ask you to send a crash report via email, actually, if it hasn't been installed from Google Play. Hm. But otherwise, in About -> Show logs, you can filter to only show errors. A crash should appear there, too. |
|
I don't know if the email prompt came up, but I was just trying to get mapping, so I didn't send it at the time... There were no errors in the in-app logs. Of course I haven't had any issues since I posted this, but if I do again, I'll send the email if it lets me. |
|
I've received two crash reports with the identical crash via email. I guess it must be that one: That's on MapLibre though and indeed already has been reported. maplibre/maplibre-native#2432 MapLibre folks are reworking this part, but because this rework has breaking changes, it will be included in the next major release, which may take a while to be released. So we are a bit in a pickle here. Should we do a major release with a crash issue that triggers apparently that often? (I.e. so that Android displays this "StreetComplete has stopped working" dialog several times while the app is in background) |
|
In any case, nothing we can do here. An option could be to submit a patch upstream that just catches and ignores the exception. |
|
Sent a crash log email just now just in case. It does look like it's the same one as you mentioned. Unfortunately, my workaround from last time didn't work this time... Thanks for trying to work this out. |
riQQ
added
upstream
|
I've had similar crashed on Samsung Galaxy S23+, Android 14. SC v59.0-alpha1 was in background for several minutes (during which I was in another GPS app), and then SC crashed by itself while in background (I have LogFox which notices/logs crashed and opens a notification/toast). Trying to restart SC several times just lead to it auto-crashing again, without offering to send logs. First crash is similar: Java / java.lang.IllegalMonitorStateExceptionbut it is followed by different one: JNI / null pointer dereference |
|
It is not a similar crash, it is the same crash. |
|
Going to reopen this because the user-perceivable crash rate seems so high that v59.0 shoudl not be released without some sort of fix. |
|
Same symptoms for me. Pixel 8a, android 14 |
|
I can confirm this, Android 12 with a MIUI device. Sometime a couple of crashes in I can launch the app and it is stable. I wrote a log with Android Studio (filtered for "streetcomplete"): I did the same for SCEE, here. |
|
Crash occurs for me as well if I'm in airplane mode. |
|
MapLibre 11.2.0 with the fix for this issue is available. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm not sure if this is related to the issues mentioned in #5693, but I thought I'd mention it. When I downloaded this version last night, it worked fine. Then this morning, it crashed a few times on startup, then started working randomly. I was playing around with it back at home, and it was working fine. I closed the app. Then when I next looked at my phone, an alert popped up that StreetComplete had crashed (even though I thought it was closed). Trying to start it then didn't work, crashing every time, even after wiping the cache, force-stopping the app, and restarting the phone.
The workaround I found was to turn off all networks, then open, then turn back on networks. Then it works fine. So when it started working randomly this morning, I'm guessing it was switching between wifi and data at just the right time.
The text was updated successfully, but these errors were encountered: