Skip to content
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

After upgrading to Flutter 3.0 I can't run applications with fluent_ui🐛 #327

Closed
andrelrf1 opened this issue May 12, 2022 · 2 comments · Fixed by #325
Closed

After upgrading to Flutter 3.0 I can't run applications with fluent_ui🐛 #327

andrelrf1 opened this issue May 12, 2022 · 2 comments · Fixed by #325

Comments

@andrelrf1
Copy link

Describe the bug
After the last Flutter update I could no longer run applications with fluent_ui for testing and not even in release mode.

To Reproduce
Steps to reproduce the behavior:

  1. Upgrade to Flutter 3.0;
  2. Run a project that has fluent_ui;
  3. The error will appear in the terminal

Expected behavior
I expected the application to start correctly.

Screenshots
image

Additional context

  • I'm using Flutter 3.0;
  • I'm using Windows 11 on the latest public build.
@bdlukaa bdlukaa linked a pull request May 12, 2022 that will close this issue
3 tasks
@jtdLab
Copy link
Contributor

jtdLab commented May 12, 2022

Same problem here

@Dancovich
Copy link

The issue seems to be on selection_controls.dart.

On line 19 the method buildToolbar is overriden from TextSelectionControls, but the super method changed signature and now receives a ClipboardStatusNotifier? instead of a ClipboardStatusNotifier.

The error message also has a bunch of warnings about calling WidgetsBinding.instance!.[something]. WidgetsBinding.instance no longer returns WidgetsBinding? so the ! operator is unnecessary. I don't believe this has anything to do with the error though, it's just a warning.

Maybe other errors will appear once this is fixed. Right now fluent_ui seems to not be compatible with Flutter 3.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants