-
-
Notifications
You must be signed in to change notification settings - Fork 541
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
No named parameter with the name 'onPopInvoked' #1359
Comments
Please, add more information about this issue. |
@deandreamatias same here. I just build apk from the Macbook and it shows this error |
same here |
Ok. |
Wouldn't it be better for you to fix it than asking us to downgrade flutter? |
You need downgrade package version, not Flutter. |
…9.2.1 chore(release): #1359 9.2.1
I release a new version 9.2.1 that update Flutter versions constraints to try avoid this error |
thank you sir! |
I have this error after installing when it was already installed. Now cannot run application at all. I need a fix. Flutter needs to work on making this never able to happen or it will not last. To fix this issue got to code they wrote and delete two lines canPop: .. and onPopInvoked: ... . Should never have been released if there was errors and as a dev I should not be having to delete lines of flutter code to have it compile. |
when i try to run it gives me result: |
Is there an existing issue for this?
Package/Plugin version
flutter_form_builder: ^9.2.0
Platforms
Flutter doctor
Flutter doctor
[✓] Flutter (Channel stable, 3.13.8, on macOS 14.0 23A344 darwin-arm64, locale en-IN)
[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] Connected device (3 available)
[✓] Network resources
• No issues found!
Minimal code example
Code sample
Not able to run
Current Behavior
Error
Expected Behavior
Should be run
Steps To Reproduce
N/A
Aditional information
No response
The text was updated successfully, but these errors were encountered: