Tidal issue after update to 2025073000

ladyofcythera

I am also having this issue, same OS and tidal version.

From playing around with it:

It only happens in profiles other than the owner (tested on two other profiles)
Does not happen with antennapod or VLC
Neither end session or device restart helps
Setting background usage to unrestricted doesn't fix it
Neither does turning on exploit compatibility mode

dangerous-orange

ladyofcythera also experiencing this issue, however, in the Owner profile

ladyofcythera

Tidal log from just after I locked the screen while playing music here

gos94584958

Can confirm, having the same issue with Tidal and GOS version 202507300. When putting Tidal in the background it just dies entirely. The bug is happening in the main/owner profile (no other profiles on device/no private space).

I see in logs:

FATAL EXCEPTION: main
Process: com.aspiro.tidal PID 9524
AndroidRuntime: java.lang.RunTimeException: Error receiving broadcast intent {act=android.intent.action.SCREEN_OFF}

gos94584958

Similar to @ladyofcythera

The crash details (taken from their log above):

--------- beginning of crash
08-01 15:04:36.443 5523 5523 E AndroidRuntime: FATAL EXCEPTION: main
08-01 15:04:36.443 5523 5523 E AndroidRuntime: Process: com.aspiro.tidal, PID: 5523
08-01 15:04:36.443 5523 5523 E AndroidRuntime: java.lang.RuntimeException: Error receiving broadcast Intent { act=android.intent.action.SCREEN_OFF flg=0x50200010 } in com.sony.sonycast.sdk.s@e5eaa96
08-01 15:04:36.443 5523 5523 E AndroidRuntime: at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0(LoadedApk.java:1852)
08-01 15:04:36.443 5523 5523 E AndroidRuntime: at android.app.LoadedApk$ReceiverDispatcher$Args.$r8$lambda$mcNAAl1SQ4MyJPyDg8TJ2x2h0Rk(Unknown Source:0)
08-01 15:04:36.443 5523 5523 E AndroidRuntime: at android.app.LoadedApk$ReceiverDispatcher$Args$$ExternalSyntheticLambda0.run(D8$$SyntheticClass:0)
08-01 15:04:36.443 5523 5523 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:995)
08-01 15:04:36.443 5523 5523 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:103)
08-01 15:04:36.443 5523 5523 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:248)
08-01 15:04:36.443 5523 5523 E AndroidRuntime: at android.os.Looper.loop(Looper.java:338)
08-01 15:04:36.443 5523 5523 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:9106)
08-01 15:04:36.443 5523 5523 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
08-01 15:04:36.443 5523 5523 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:593)
08-01 15:04:36.443 5523 5523 E AndroidRuntime: at com.android.internal.os.ExecInit.main(ExecInit.java:50)
08-01 15:04:36.443 5523 5523 E AndroidRuntime: at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
08-01 15:04:36.443 5523 5523 E AndroidRuntime: at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:371)
08-01 15:04:36.443 5523 5523 E AndroidRuntime: Caused by: java.lang.IllegalArgumentException: listener not registered
08-01 15:04:36.443 5523 5523 E AndroidRuntime: at android.net.nsd.NsdManager.getListenerKey(NsdManager.java:1270)
08-01 15:04:36.443 5523 5523 E AndroidRuntime: at android.net.nsd.NsdManager.stopServiceDiscovery(NsdManager.java:1638)
08-01 15:04:36.443 5523 5523 E AndroidRuntime: at com.sony.sonycast.sdk.ScMediaRouteProvider.stopDiscovery(Unknown Source:117)
08-01 15:04:36.443 5523 5523 E AndroidRuntime: at com.sony.sonycast.sdk.ScMediaRouteProvider.access$200(Unknown Source:0)
08-01 15:04:36.443 5523 5523 E AndroidRuntime: at com.sony.sonycast.sdk.s.onReceive(SourceFile:80)
08-01 15:04:36.443 5523 5523 E AndroidRuntime: at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0(LoadedApk.java:1844)
08-01 15:04:36.443 5523 5523 E AndroidRuntime: ... 12 more

I am seeing the same error in my log too. @GrapheneOS is this a OS bug or an app level bug? wondering if there's any work around.

GrapheneOS

gos94584958 It appears to be an app bug triggered by one of the new VPN lockdown enhancements we added. We can add a workaround for this app for a future release. It won't stop the rollout of this release.

mills559

Checked the logs, same issue for me too. If anyone finds a workaround before the next update let me know. I'll do the same.

Thanks

Probably9857

Just out of curiosity....

Is everyone experiencing this issue using a VPN and blocking non-VPN connections?

Since the issue is related to VPN lockdown mode, is it possible that allowing non-VPN connections might be a workaround (if you don't mind risking some VPN leaks)?

ladyofcythera

Probably9857 okay yeah I just tested it with the block connections without vpn setting off and after restarting the VPN it works.

Turns out I forgot to turn the setting back on in the owner profile at some point which is why it wasn't effecting it.

Thanks all

chrisonadventures

Probably9857
Nice! Thanks so much for sharing this - really appreciate it. Was driving me nuts. This workaround worked perfectly for me. Now happily awaiting the next update to hopefully get a fix.

situated_browsing549

ladyofcythera this worked for me as a temporary work around as well. Thanks for sharing.

GrapheneOS

The bug in the Sony SDK used by the Tidal app has been worked around for our next OS release. It's a bug in the SDK which is uncovered by our improved VPN leak blocking rather than an issue with the way we implemented it. The app is handling the API incorrectly and could crash in other cases without our changes.

themaestr0

GrapheneOS Thank you for taking the time to implement a work-around in the OS for this bug.

Out of curiosity, do you think there are any reasons to believe that what they're doing is actually resulting in a connection that is leaked outside of the VPN used in the device?

Truckfish

Obviously not a long term solution but a workaround that helped me:
Go to offline mode in Tidal, open the app settings and remove network permissions, restart Tidal and listen to the downloaded music with no problems.
If you want to find/download something new you have to reverse everything of course.
Hope this helps

phone-company

This issue should be fixed in the newest Alpha Version