lovegaoshi

i wonder if wakeLock has any effect on context.startForegroundService? theorrtically it just keeps the background service alive also not sure how generalizable this should be since Google's against this for...

okay, I'm willing to investigate further, there's clearly something wrong with how the MusicService is started. I'm not an android expert but if I just observe what's in dev options...

ok. For those interested: enable dev options and watch the RNTP app in the running state and cache state. When playing the process should have musicService attached. when the app...

if anyone can disable stopForeground like this https://github.com/lovegaoshi/react-native-track-player/commit/9afe35b163c84bf69ba484699dc8aac94dfc00cb and report back findings it would be nice. I cannot reproduce the error message what so ever

ur welcome to try https://github.com/doublesymmetry/react-native-track-player/commit/1145e2da93647cab93bf118cbf22177433fbe642 for android 14 though i doubt it matters. unless someone can reliably reproduce this error there aint much to do other than not stopping tje...

you're triggering this via setupPlayer? so this happens at app start up?

the trace log specifically occurs at MM.setupPlayer which is the RN module, where TP.setupPlayer calls it, not when audio is first played; do you use await TP.setupPlayer? and why is...

so your app reliably crushes with this exception on android 14? is your component rerendered somehow and triggering componentDidMount again? if you console.log within that is it called twice? and...

then when is your TP.setupPlayer called? if its truly on component render your app cannot be in background at all

wdym play audio in the background, via the notification panel? i'm still not clear why/how youre triggering TP.setupPlayer. if you put a console.log within TP.setupPlayer theoretically you should see it...