[BUG] - Immediate crash on launch on 4.17.0 on GrapheneOS

[tomorrow-nf]

After updating to 4.17.0 (https://github.com/eddyizm/tempus/releases/download/v4.17.0/app-tempus-arm64-v8a-release.apk) the app is failing to launch on GrapheneOS, immediately crashes with a generic crash error message and the following stack trace:

java.lang.RuntimeException: Unable to create service com.cappielloantonio.tempo.service.MediaService
at android.app.ActivityThread.handleCreateService(ActivityThread.java:5593)
at android.app.ActivityThread.-$$Nest$mhandleCreateService(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2745)
at android.os.Handler.dispatchMessage(Handler.java:132)
at android.os.Looper.dispatchMessage(Looper.java:333)
at android.os.Looper.loopOnce(Looper.java:263)
at android.os.Looper.loop(Looper.java:367)
at android.app.ActivityThread.main(ActivityThread.java:9332)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:566)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:837)
Caused by: java.lang.RuntimeException: Mapping failed for song ID: dy3eKOrEoOoLiJUE5bYfW5
at com.cappielloantonio.tempo.util.d.w(SourceFile:957)
at com.cappielloantonio.tempo.util.d.A(SourceFile:19)
at com.cappielloantonio.tempo.service.MediaService.onCreate(SourceFile:585)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:5582)
... 10 more
Caused by: java.lang.NullPointerException: Attempt to read from field 'java.lang.Object N2.c.f' on a null object reference in method 'java.util.HashMap Z2.b.e()'
at Z2.b.e(SourceFile:21)
at com.cappielloantonio.tempo.util.l.h(SourceFile:6)
at com.cappielloantonio.tempo.util.d.r(SourceFile:129)
at com.cappielloantonio.tempo.util.d.w(SourceFile:9)
... 13 more

Crash was resolved by completely wiping user data and setting up the navidrome connection again from scratch

[eddyizm]

Hi @tomorrow-nf
that's a bummer, sorry to hear. I have seen this before but have not been able to determine what the actual cause is. It seems to happen specifically with navidrome back ends (i believe)
Its it either that or some database migrations in this release.

[chicknlil]

Second Update: Changing the transcoding on the default browser UI to aac on all players (including Tempus), then force closing Tempus, clearing data/cache and putting my info back in did the trick for me. NOTE: I had to do the data/cache clear; it didn't work for me otherwise. So @tomorrow-nf , maybe this will help you?

Update: Rebooting my Navidrome instance made no difference and I'm on their most recent stable release.

Have basically the identical issue, though I updated today to the latest stable release and that didn't solve it. My logs below. Also, given your Navidrome backend comment, I'm going to restart mine, see if that helps or resolves it.

java.lang.RuntimeException: Unable to create service com.cappielloantonio.tempo.service.MediaService: java.lang.RuntimeException: Mapping failed for song ID: ExQEvRvY1sHgzXpkn54iMi
at android.app.ActivityThread.handleCreateService(ActivityThread.java:5714)
at android.app.ActivityThread.-$$Nest$mhandleCreateService(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2877)
at android.os.Handler.dispatchMessage(Handler.java:115)
at android.os.Looper.loopOnce(Looper.java:302)
at android.os.Looper.loop(Looper.java:412)
at android.app.ActivityThread.main(ActivityThread.java:9998)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:613)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1074)
Caused by: java.lang.RuntimeException: Mapping failed for song ID: ExQEvRvY1sHgzXpkn54iMi
at com.cappielloantonio.tempo.util.d.w(SourceFile:957)
at com.cappielloantonio.tempo.util.d.A(SourceFile:19)
at com.cappielloantonio.tempo.service.MediaService.onCreate(SourceFile:585)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:5684)
... 9 more
Caused by: java.lang.NullPointerException: Attempt to read from field 'java.lang.Object N2.c.f' on a null object reference in method 'java.util.HashMap Z2.b.e()'
at Z2.b.e(SourceFile:21)
at com.cappielloantonio.tempo.util.l.h(SourceFile:6)
at com.cappielloantonio.tempo.util.d.r(SourceFile:129)
at com.cappielloantonio.tempo.util.d.w(SourceFile:9)
... 12 more

[eddyizm]

@chicknlil are you on graphene OS as well?
Your work around was basically what @tomorrow-nf ended up doing as well.

I'm not sure what the root cause is. It seems like something is cached and/or the db migrations aren't able to deal with it.

The last time this happened, a clean install was basically the way around it although we tried to deal with several NPEs.

[chicknlil]

@chicknlil are you on graphene OS as well?

I'm on I believe Oxygen OS? Whatever OnePlus puts on phones.

And on my end it may have timed in with recent Proxmox updates, but I'm not even sure of THAT either.

[eddyizm]

And on my end it may have timed in with recent Proxmox updates, but I'm not even sure of THAT either.

I don' think it is anything external unfortunately.

[tvillega]

@eddyizm both crashes returned the exact same stack trace, so the issue is still around somewhere and getting triggered on each update. Should we de-obfuscate the stable releases a bit to be able to capture where it happens?

I've been reading about that here:

• https://stackoverflow.com/a/61705347
• https://stackoverflow.com/a/6670172

Edit: Wait, there seems to be a mapping file to get the names back from the obfuscation!
Edit2: This article shows how to de-obfuscate the stack trace when having a mapping file at hand.