-
Notifications
You must be signed in to change notification settings - Fork 553
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
[BUG]: app crashes after call startRecorder on iOS 17.4 simulator #1032
Comments
Thank you @vickychu for this very clear and complete issue. |
@vickychu |
Do you use startRecorder fromStream ? I want to rewrite all the code about streams but this is a major work and I have not much time. I am really found of streams on Flutter Sound. This is a really important feature that I want to run flowlessly. In the mean time you can try to await the end of setSubscriptionDuration before startRecorder. There is a possibility that it will fix your crash. |
@Larpoux
Still thanks for you suggestion. The real device is ok. I can still work with the real device. |
I have the same problem when starting the recorder on iOS to a stream |
There is actually a big problem on iOS when recording to Streams or when recording to Raw PCM. It used to work, but not anymore (regression). I have not found the reason of the problem. I have not much time to spend on Flutter Sound maintenance and someone else should try to debug that. I am actually in the process of rewriting all the code about RAW PCM on iOS, but this is much work and do not expect to have this issue fixed soon. |
Flutter Sound Version : 9.4.6
├── flutter_sound 9.4.6
│ ├── flutter_sound_platform_interface 9.4.6
│ ├── flutter_sound_web 9.4.6
│ │ ├── flutter_sound_platform_interface...
Severity
Platforms you faced the error
Describe the bug
My app crashes after I call the function "startRecorder" on the simulator (ios version is 17.4).
Everything is ok if the ios version of the simulator is 16.
Everything is ok if I run the app in real device, even the ios version of the device is 17.3.
I think I'v met the same issue as #1007.
To Reproduce
Steps to reproduce the behavior:
Logs!!!!
The text was updated successfully, but these errors were encountered: