[4.1.1] MusicService.startAndStopEmptyNotificationToAvoidANR

[amm4ryous4f]

Describe the Bug
Issue only on android
Unable to start service com.doublesymmetry.trackplayer.service.MusicService@3d6fb9d with null: android.app.ForegroundServiceStartNotAllowedException: Service.startForeground() not allowed due to mAllowStartForeground false: service com.dynamite.digital/com.doublesymmetry.trackplayer.service.MusicService

Steps To Reproduce
This issue is reported by firebase repeatedly.

Environment Info:

react-native-track-player : 4.1.1
System:
OS: macOS 15.3.1
CPU: (8) arm64 Apple M3
Memory: 125.28 MB / 8.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 23.7.0 - /opt/homebrew/bin/node
Yarn: 1.22.22 - ~/Documents/Office/TheSource/TheSource/node_modules/.bin/yarn
npm: 10.9.2 - /opt/homebrew/bin/npm
Watchman: 2025.02.10.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.16.2 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 24.2, iOS 18.2, macOS 15.2, tvOS 18.2, visionOS 2.2, watchOS 11.2
Android SDK: Not Found
IDEs:
Android Studio: 2024.2 AI-242.23726.103.2422.13016713
Xcode: 16.2/16C5032a - /usr/bin/xcodebuild
Languages:
Java: 17.0.14 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.19 => 0.71.19
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found

[lovegaoshi]

u can find a plethora of issues in the tracker reporting the same problem.
without any reproducible steps there is little meaning opening a new issue here. ur best bet without a reproducer is to migrate to media3, since they added a lot of workarounds on this in 2022-2024.