c.goettert

Are you using `buildToolsVersion = "34.0.0"`? I guess it's basically the same issue as [this one](https://github.com/joltup/rn-fetch-blob/issues/866 ).

Basically this [new requirement](https://developer.android.com/about/versions/14/behavior-changes-14#runtime-receivers-exported) forces you to pass a `RECEIVER_EXPORTED` or `RECEIVER_NOT_EXPORTED` value when registering a new receiver, e.g.: `context.registerReceiver(broadcastReceiver, intentFilter, RECEIVER_NOT_EXPORTED);`. The problem is, the only `registerReceiver`call I can...

I was facing this issue with version `4.0.0-rc04` of react-native-track-player. The player was crashing on android with the `RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED` error. However, after upgrading to `4.1.1` the issue is...

I am facing the same issue..

+1

I am facing the same issue (using react-native: 0.72.15). Downgrading to `4.0.0-rc04` fixes the issue for me which shows it's not a network issue...

@Brightbong92 did you find any solution to this?

Thanks for posting you solution @Brightbong92 . Indeed I found out that for me it was something else that has caused the bug: I was calling `TrackPlayer.reset()` immediately before starting...

This problem should be prioritised to keep this (really helpful) library alive. What about the related [pull request](https://github.com/doublesymmetry/react-native-track-player/pull/2370/), is there any plan when it will get merged?

I don't belong to Realm, but I would still be happy if you could manually re-create the PR, so eventually it gets merged 👍 . Snyk also complains to me...