[6.1.1 crash report] 6.1.1 crashes on Samsung devices

[Andy Hon]

Hi, Gareth!
6.1.1 update brought app crashes on my Galaxy S22 (S901N, Android 14) and Galaxy Tab 8.0 (T290, Android 10) devices. Opensongapp crashes voluntarily without notice, just exiting to home screen (see video attached).  

I noticed three scenarios:
1) Crash on exporting a screenshot (while app trying to render the screenshot)

2) Crash when entering Font setting.

3) On T290 sometimes crashes on app start.

6.0.9 works fine.
Somewhat a newly added code in 6.1.1 causes crash. Could you revert it or troubleshoot that? Thanks a lot!

bugreport:

https://drive.google.com/file/d/1WCYUDTgjSAxBEBxtPuX7jrGpB8LbtDMz/view?usp=sharing

video:

https://drive.google.com/file/d/1gxV8kcVElVY7_R4GH0JsTLJdmzUqeY9v/view?usp=sharing

[Andy Hon]

Crashlog from S22 device:

[Gareth Evans]

Hi Andy,

Thanks for the video and crash logs.  The CrashLog.txt file is the simplest (and best) thing to send me.  I trawled the 170MB Android bug log and found the same small crash code as the CrashLog.txt file!  This file only records crashes caused by OpenSongApp and doesn't record all the extra stuff, so send that as the first option.

The export issue, the CrashLog.txt and the main Android debug log all point to the same error - a blank section of lyrics somewhere when exporting.  I've put in a catch for that so it shouldn't happen again.

The fonts crash, I can't see anywhere in the logs, can you send me the CrashLog.txt file on the device that crashes on this action please.

The hardware acceleration switch isn't causing a crash.  To enable or disable this, the app needs to be closed and restarted again - this is what is happening.

Best wishes and thank for taking the time to help make the app better!

Gareth

[Andy Hon]

Thanks for your detailed reply.

Interesting thing is that Crashlog.txt isn't being updated after such crashes.

I've even tried to delete Crashlog.txt - no new log file was created. 

App unloads very fast - in a few milliseconds.

But this behavior is the same when entering Font setting, and when trying to export set.

Noticed that exporting set as Image as well as Screenshot leads to crash.

And another bizarre thing - exporting single song as image/sxreenshot works fine. Only exporting set is impaired.

[Andy Hon]

Sharing filewriteactivity.txt log - maybe it will be useful.

[Andy Hon]

upd: Importing .osts set file also leads to such crash. But after restart set is filled successfully with the songs contained in that .osts file.

[Andy Hon]

upd:

Sorry for so much messages, but I found that useful for troubleshooting:

Permission "Nearby devices" switched to allowed leads to app crash on start. See video.

https://drive.google.com/file/d/1-OuFVXedFwkBBkMcjGHY5u_Uqslwfksk/view?usp=drivesdk

[Andy Hon]

upd 😊:

I've found it - "Web server" feature being enabled leads to app crash on start.

When "Nearby devices" permission is allowed and Web server is off, app starts normally.

Please don't ask me how I've noticed that - I don't know 😄

[Gareth Evans]

Hi Andy,

I managed to get one of my devices to do something similar when switching on the webserver and have traced it down to a bit of testing code that I left switched on (called StrictMode) that if it sees something it isn't expecting, or is potentially dangerous (e.g. checking internet connection) it can throw a crash by simply shutting down - no crash log!

I've placed a test.apk file in the downloads folder that I'm hoping will address at least some of your crashes.  I usually don't push bug fixes on Friday-Sunday as this is when the app is being used most often, but given that this causes real stability issues, I'll push it to the Play Store now, but it usually takes a few hours to go live.

Many thanks for your help with this!

Gareth

[Andy Hon]

6.1.2 tested successfully, everything's fine now.

Many thanks! Agile as always 😉😊