-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App crashes immediately after attempting to initialize TrackPlayer #2412
Comments
@Mirott Currently experiencing the exact same issue with the same setup. Have you had any luck resolving this? |
@Mirott I was able to get this working with expo by using the 3.x release. fwiw i also had the issue with the nightly release.
|
|
I suppose it's because of the new architecture on Expo 52, too. The app crashes instantly, without even initializing. Hope it will get fixed asap. Will try version 3 for now... |
With version 3 it does not work for Android |
Letting everyone know I am getting this issue as well on iOS. No matter if I am on simulator or real device. App crashes instantly anytime I put anything related to react-native-track-player in my project. I can confirm that installing react-native-track-player@3 worked and my app is no longer crashing on load. I hope this gets fixed soon or if I can add any insight or help I will do my best. |
try disabling the new architecture and rebuilding your project. react-native-track-player isn't compatible with the new architecture. you can enable the new architecture when rntp releases a compatible update. |
Describe the Bug
The app disappears from the foreground immediately after attempting to execute the code TrackPlayer.registerPlaybackService or TrackPlayer.addEventListener
The console does not show anything.
The only thing that appears is a MacOS crash message with the error information:
Crashed:: com.facebook.react.runtime.JavaScript
Steps To Reproduce
Code To Reproduce
Environment Info:
Real device? Or simulator?
Both
What OS are you running?
MacOS 15.0.1
The text was updated successfully, but these errors were encountered: