doublesymmetry / react-native-track-player

A fully fledged audio module created for music apps. Provides audio playback, external media controls, background mode and more!
https://rntp.dev/
Apache License 2.0
3.25k stars 1k forks source link

Track Player button does not do anything (after upgrading to 4.0.1) #2269

Closed nl-danish closed 5 months ago

nl-danish commented 6 months ago

Describe the Bug After upgrading the package to 4.0.1 from 3.2, On closing the app once any track is played using react-native-track-player package's track player it opens up the tray (miniplayer) with the track's name and album but no end timestamp and it does not react to the play button or any other podcast operational buttons (rewind, play, pause). Steps To Reproduce How can someone else reproduce this bug?

  1. Open the app
  2. Play any track for some time
  3. Close the app
  4. Open the app again
  5. Try to click the track from mini player.

Code To Reproduce Not possible to post the whole code here, but this did not used to happen while we were in 3.2, we upgraded to 4.0.1 and ever since, it's been happening

Environment Info: npx react-native info : System: OS: macOS 13.3.1 CPU: (8) arm64 Apple M1 Memory: 113.25 MB / 8.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 18.16.0 - /opt/homebrew/opt/node@18/bin/node Yarn: 1.22.19 - /opt/homebrew/bin/yarn npm: 9.5.1 - /opt/homebrew/opt/node@18/bin/npm Watchman: 2023.05.22.00 - /opt/homebrew/bin/watchman Managers: CocoaPods: 1.12.1 - /Users/appName/.rvm/gems/ruby-2.7.6/bin/pod SDKs: iOS SDK: Platforms: DriverKit 22.1, iOS 16.1, macOS 13.0, tvOS 16.1, watchOS 9.1 Android SDK: Not Found IDEs: Android Studio: 2022.2 AI-222.4459.24.2221.9971841 Xcode: 14.1/14B47b - /usr/bin/xcodebuild Languages: Java: 11.0.19 - /usr/bin/javac npmPackages: @react-native-community/cli: Not Found react: ^17.0.2 => 17.0.2 react-native: ^0.66.5 => 0.66.5 react-native-macos: Not Found npmGlobalPackages: react-native: Not Found

Real device? Or simulator? Both What OS are you running? Mac 13.3.1 (22E261)

How I can Help What can you do to help resolve this? We as a team are going through the code base of JS and Android, both. Have you investigated the underlying JS or Swift/Android code causing this bug? We are trying to. Can you create a Pull Request with a fix? Yes, if we found the fix

dcvz commented 6 months ago

Did you follow the migration guide? https://rntp.dev/docs/next/v4-migration

jspizziri commented 5 months ago

Closing this due to inactivity. Please create a repro in the example project based on a fork and we can reopen.