Gav Richards

@hyochan would you be able to check on this for me? I'm very keen to begin using your excellent library :) Thanks

That does appear to be correct. I can't understand why it's coming through with the type `audio/x-m4a`, when if you use React Native Audio Toolkit, you get `audio/aac` as expected.

@efstathiosntonas Thanks but I'm not sure I understand how that is related to it reporting a position of 572 seconds, less than a second into recording.

This is a log of what I get from the addRecordBackListener event. It appears that `currentPosition` here represents milliseconds perhaps? But the README clearly suggests it is seconds. ``` LOG...

This time a log from Android, similar result: ``` LOG {"e": {"currentPosition": 502}} LOG {"e": {"currentPosition": 1003}} LOG {"e": {"currentPosition": 1504}} LOG {"e": {"currentPosition": 2004}} LOG {"e": {"currentPosition": 2504}} LOG...

@jspizziri `2.1.2`

1. You can use this library's `useTrackPlayerEvents` hook and check for an `event.type` of `Event.PlaybackError`. You'll see that if you lose connection while playing, this is only triggered on Android....

Just ran into this. Got the error "Your binary indicates that your app tracks users. - Your app indicates that you track users.". We have previously submitted an update for...

I'm also having the exact same problem with the conflict between the these libraries and the disappearing lock screen controls. Would love to know if anyone found a solution.

Yes I switched to [this fork](https://www.npmjs.com/package/@meditatio/audio-toolkit), which has [a fix for the issue](https://github.com/meditatio-app/react-native-audio-toolkit/commit/b6e803f15b976db048c4096f0d882e502102ca98).