-
Notifications
You must be signed in to change notification settings - Fork 27.2k
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
'WidgetsBinding' runtime warnings using 3.0.0 stable release #103561
Comments
@pattobrien Did you find any temp fix for this? |
The same problem was found |
same warnings for me |
nope, no workaround found yet. |
You can just ignore these warnings for now :) |
Can somebody try to run |
fixed them all in my code, but I get messages from dependencies which is quite annoying |
Ran Can we somehow suppress the warnings in third party dependencies? - It makes logs unreadable on flutter test |
These warnings could also be the result of the fact that Flutter 3 introduces nullability changes to WidgetsBinding. |
This fixed my issue from here: #103571 (comment) |
This issue has NOT gone away for me after running dart fix --apply unfortunately. Below is the only thing that shows in my terminal as an error and not a warning. `Error: The non-abstract class 'GaMaterialLocalizations' is missing implementations for these members:
|
Facing same issue
|
This command NOT helped me |
Circling back on this issue, the warnings seems to be coming from framework itself and as mentioned earlier, could be related to #89451 If the warnings are coming from community plugins / packages, the fix need to be made in respective packages. Based on the report and the traction received for this issue, I am going ahead and labeling it for further insights from the team. /cc @Hixie |
same for me as well. console is being clogged by these warnings. |
+1 |
A temporary solution is downgrading: |
dart fix --apply doesn't work. thanks. |
if you are using device preview package. |
the flutter pub upgrade did fix my crash that prevent me from build. i guess some packages really needs to upgrade/check if its compatible with v3 |
dependencies needs to be upgraded!!, wait for the authors to update the dependencies. |
Those warnings are coming from third-party plugins compiled against the older version of flutter, Updating the plugin code with originally filed here #101497 (closed) |
Upgrading my Kotlin version (manually), did the trick. You can do that in your
|
doing the same thing, not work for me. |
This comment was marked as abuse.
This comment was marked as abuse.
Any update ? |
Same here, upgraded to Flutter 3 and created a brand new app and getting:
|
The same issue 💻 |
The same issue here. As far as I understand now, you can either ignore the warnings from third-party dependencies, or roll back to the previous version and wait until the dependency versions are updated to compatible with flutter 3.0. |
The app will not build. It is stated that they are only warnings but in my case the app will not build. So I can not ignore the warnings. /E:/Flutter/.pub-cache/hosted/pub.dartlang.org/syncfusion_flutter_core-20.1.55/lib/src/legend/legend.dart:548:30: Warning: Operand of null-aware operation '!' has type 'SchedulerBinding' which excludes null.
FAILURE: Build failed with an exception.
BUILD FAILED in 38s |
@RudyLie1988 the issue is not my own code but all the libraries and packages that I do not have control over also has them in. Yes I can remove it from my own code but your fix will not fix all the libs I am using. I did a Dart --fix and it removed all the ! from my own code but not the libs. And people say it should not stop the build. Yet it does break the build. |
i want to know how to ignore it? plz. |
Just don't look at it |
@jnthnklvn are you trying to be funny? I can not ignore it as the build fails as I showed above. So not looking at it won't help. |
No, I'm not. I was answering just about his mention. In your case could be this: |
All works 100% and compiles using 2.10.5. After I upgrade to version 3 I get all these errors and the build will fail.
|
@JacoFourie, the error appears to have something about this:
May you can try to update that package and see if the build problem solves... |
If you are getting an error please file a separate bug. |
I'm going to close this issue since I think we understand it well now. The underlying issue of showing warnings about dependencies is an issue we will resolve on the Dart side via dart-lang/sdk#46264. If you are only getting warnings, meaning the app still runs, you may ignore them, they are harmless, and do not indicate a problem. As your dependencies update, the warnings will go away. If you are getting errors, or if you appear to only be getting warnings but the app nonetheless does not build or execute, please file a new bug and we will try to determine the cause and resolve those issues. Make sure to include full logs from Thank you for your continued use of Flutter! |
Pre-Requisites
Steps to Reproduce
flutter create test_app
to create a new appflutter run
to build and run appExpected results:
No warnings in debug console.
Actual results:
The following warnings are seen:
Code sample
Logs
The text was updated successfully, but these errors were encountered: