deckerst
App crashed while trying to set the GPS location to a photo
Describe the bug I tried to set the location for a photo, but app crashed - it exited to android UI. When I tried to switch back to it with using android taskbar, it cold started.
To Reproduce The issue is not reproduced at will, but this is what I was doing:
- Opened a photo without GPS coordinates to a fullscreen view
- Swiping it up
- Opening a [...] menu to edit location
- Clicked on map, selected location, confirmed it - then app exited
I also noticed, if I open a full map (by clicking on a map icon from a photo which is having GPS coordinates) many times for different photos, at some point phone becomes very unresponsive, like Aves is somehow memory leaking (Map widgets are created but not destroyed?).
Why am I so sure it's Aves? Because if I kill it from Android task manager, the phone responsiveness returns back to normal almost instantly.
I wonder if they're tools like top/htop/btop exist for Android so I could confirm this :)
I think I nailed it down and can reproduce at will. Here's what you need to do:
- open any photo, which has a GPS, to be shown at fullscreen (basically tap on it in a collection)
- swipe it up, and wait till minimap will appear
- swipe it down to return back to the mode when just photo is displayed fullscreen
- keep swiping up and down, and after few more turns you'll see the app crashes
You might need a number of attemps, like from 5 to 10, and you don't have to wait till the minimap becomes completely rendered
Thanks for the report. Alas, it's a good news / bad news situation.
The good news is that you stumbled upon a known issue that has already been reported to Google by many people:
- https://github.com/flutter/flutter/issues/105965
The bad news is that Google hasn't fixed it yet, and there's nothing Aves can do to fix it on the app side.
Also, I tried many times to follow the steps you mentioned, but I can't reproduce the crash on my device. It's strange because my device is the same as yours (S10e with Android 12).
It's actually good news, because when I switch to OpenStreetMap - I don't have this bug :)
Yeah, it's kind of hard to reproduce it on purpose. I can provide a video on how to do that. I realized it's all about timings: if you're lucky enough to swipe down at the moment when map is about to be shown, app crashes.
https://user-images.githubusercontent.com/110789576/190450405-82a9ca7d-3028-40d7-a329-56595245426b.mp4
Hello there! I've seen you added a label "works for me". Does it mean something has changed (like framework was updated) and I can update & retest it?
No, i believe it's still not fixed, so some people may experience this. I've just not personally experienced it so far.
@kha84 actually, I haven't seen error reports for this issue in a long while, so I guess it's fixed in practice, even if the Flutter issue mentioned above isn't marked as fixed. I'll close this issue, but feel free to comment/reopen if you experience it again.