We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I've just upgraded to 3.x.
My code did not call the initialize method before calling startRecorder.
The result was a no suchMethodError.
It would be helpful if the public api threw an exception if initialize hadn't been called.
On the other hand why can't this be handled internally? Why do we need to force the user to call it when the package could initialise itself?
The text was updated successfully, but these errors were encountered:
Yes, you are right. I will add this check in next release.
Sorry, something went wrong.
Flutter Sound 3.1.6 calls initialise() itself if the App did not do it.
No branches or pull requests
I've just upgraded to 3.x.
My code did not call the initialize method before calling startRecorder.
The result was a no suchMethodError.
It would be helpful if the public api threw an exception if initialize hadn't been called.
On the other hand why can't this be handled internally? Why do we need to force the user to call it when the package could initialise itself?
The text was updated successfully, but these errors were encountered: