Closed DennisdeWitNL closed 11 months ago
Hello @DennisdeWitNL, check this code
const RemoveStreamByButton = async () => {
await TrackPlayer.stop();
await TrackPlayer.reset();
};
Hello @DennisdeWitNL, check this code
const RemoveStreamByButton = async () => { await TrackPlayer.stop(); await TrackPlayer.reset(); };
Yep, that seems to make the notification disappear again, indeed. I will roll out an internal beta and check if my testers also have no problems anymore. :)
This should now be fixed with rc07
which was just released
This is still happening on latest version rc07 for iOS devices. Any suggestions to fix this?
This is still happening on latest version rc07 for iOS devices. Any suggestions to fix this?
Should not be. @DennisdeWitNL could you also verify whether you continue to see this?
Verified via the example app with the latest RC
This is still happening on latest version rc07 for iOS devices. Any suggestions to fix this?
Should not be. @DennisdeWitNL could you also verify whether you continue to see this?
As you might know, today was ‘shiny new toy’-day for Apple users. I am setting up my iPhone now and will tell you the results later today or tomorrow. :)
@dcvz With RC09, on iOS 17.0.2, it clears the Now Playing correctly when performing a TrackPlayer.reset()
.
Describe the Bug I am using TrackPlayer.reset(); to clear the queue and to clear the Now Playing metadata in the Control Center on Android. While it works fine on RC05, it seems to be broken on RC06. Also, it seems
Doesn't clear the NowPlaying metadata either when closing the app, while the RC05 version works perfectly fine that way. It probably is related to each other.
Steps To Reproduce
Code To Reproduce In my case I just made a button to reset the queue:
Replicable on Example App? Can you replicate this bug in the React Native Track Player Example App?
Yes, and it works fine with RC05, just a problem with RC06.
Environment Info: Paste the results of
npx react-native info
Paste the exact
react-native-track-player
version you are usingReal device? Or simulator? What OS are you running?
We have tested this against an LG Velvet (Android 12), Samsung S22 Plus (Android 13), Samsung S10 Plus (Android 12) and the emulator (Android 12). All with the same results.
How I can Help What can you do to help resolve this? Have you investigated the underlying JS or Swift/Android code causing this bug? Can you create a Pull Request with a fix?
No, I don't know Swift/Kotlin, I am a JS developer, sorry!