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
[Firebase_Database]: <Error: Exception: Unknown event type: DatabaseEventType.value> #12759
Comments
Hello @fahrezahaydar, I've tested your code in my environment, and it didn't cause any issues: Future<void> _set() async {
await FirebaseDatabase.instance.ref().child('nested/check').set(false);
} Please share a complete example where this error is occurring, so we can analyze and determine where it might be happening. |
I tried run few time. Yeah its worked, but I notice that this error will occur again every i make mistake on other code that pause debug. After solve other code and hot reload/restart, this error will occur in every set/update in my code. I dont know its flutter_web problem or the package. Its suck i must relaunch debug every i make mistake |
Can you provide some steps along with the code that causes the issue? Example for steps to provide:
|
Hey @fahrezahaydar. We need more information to resolve this issue but there hasn't been an update in 7 weekdays. I'm marking the issue as stale and if there are no new updates in the next 7 days I will close it automatically. If you have more information that will help us get to the bottom of this, just add a comment! |
Is there an existing issue for this?
Which plugins are affected?
Database
Which platforms are affected?
Web
Description
Just Simple Update with button like this :
Will execute perfectly firstly but make after couple tries will return error like this. I try using async, change set to update but still give this error
Reproducing the issue
Firebase Core version
^2.31.0
Flutter Version
3.19.5
Relevant Log Output
No response
Flutter dependencies
Expand
Flutter dependencies
snippetAdditional context and comments
No response
The text was updated successfully, but these errors were encountered: