Handle interruptions on iOS when app is in foreground/background#328
Open
julioxavierr wants to merge 2 commits intoOkelm:masterfrom
Open
Handle interruptions on iOS when app is in foreground/background#328julioxavierr wants to merge 2 commits intoOkelm:masterfrom
julioxavierr wants to merge 2 commits intoOkelm:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Now by default, the recording will be paused when an interruption begins and resumed right after the interruption ends. Works when the app is in foreground/background.
This behavior is set by default to match the behavior that happens when an interruption occurs on Android.
Also, it's possible to stop recording when an interruption occurs (on prepareRecording). In this case, the recording will be stopped and the session will be set to inactive. It's also possible to start another session after this (before, it was breaking the app because it wasn't handled properly).