Charles Reitz
Charles Reitz
Based on #607, it might be necessary (and much appreciated by the community, I'm sure).
I had the same issue a while ago and found that you need to call: `[self.volumeHandler start];` after you initialize the volumeHandler. (I'm doing it in swift, so I'm guessing...
Same issue - mentioned [here](https://github.com/react-navigation/react-navigation/issues/12278#issuecomment-2828622369)
Seeing the same issue on a nested route. Hiding the header does resolve the issue as well, but of course is not ideal
Using a custom header seems to resolve this as well
>You might want to consider implementing checks that halt the recording when the app is backgrounded and only resume it when foregrounded again, as per the documentation. Thank you maintenance...
The only "workaround" I found was to stop the recording as soon as the app is backgrounded. Not ideal, but at least the video up until that point is not...
@kculmback-eig your issue may be that you're checking for `background` state, rather than not `active`. I think the app usually goes to `inactive` before it goes `background`, and that small...