-
-
Notifications
You must be signed in to change notification settings - Fork 620
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
Crash after commit [Add movieFragmentInterval options.] when enter in background #1629
Milestone
Comments
al3x88
changed the title
After added fragment crash when enter in background
Crash after commit [Add movieFragmentInterval options.] when enter in background
Nov 21, 2024
Clash log
|
I'm able to fix the issue on our end. Thank you for reporting it. #1630 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
If I install version 2.0.0 everything works perfectly unless you can't record locally as for the change in this commit: f433315
If setup my SPM with this commit:
what happen is that, the first time I call (in viewDidLoad):
Task{ await mixer... }
and I put the app in background, it throw the error:
Incorrect actor executor assumption
and, if you are from the simulator it crashes, otherwise it restart from splash view (so basically the streaming is lost).
Note: if I comment all mixer occurrences and I test it works perfectly (unless does nothing since mixer is commented)
I tested extensively and I figured out that the behaviour happens after commit [Oct 31]:
4d19072
So most probably is related to some change happened on MediaMixer() on [Nov 1] here:
1e95f89
So currently I don't see any commit on ver 2.0.0 that allow my to record and going in background without issues.
Hope you can help me!! Many thanks for you amazing work.
To Reproduce
Incorrect actor executor assumption
Expected behavior
When app is set in background, it should be resumed without issues and keeping RTMP connection and view alive.
Version
2.0.0 commit f433315
Smartphone info.
Additional context
No response
Screenshots
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: