-
Notifications
You must be signed in to change notification settings - Fork 26.7k
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
[flutter_tools] "Unknown flutter tag" crash during flutter upgrade
#133441
Comments
Hi @dotupNET. Thanks for filing this. Please try running |
Hi. I know this Flag. But this is not the expected behaviour. I didn't change anything. |
Same error here. Like @dotupNET didn't change anything. With |
I have the same error and didn't change anything. Trying to update 3.13.0 stable. |
I upgraded with |
I have the same error and didn't change anything. And I upgraded with this command: flutter upgrade -f |
Same error. Could upgrade with |
Having the same issue. Flutter doesn't seem to want to build the app on the Pixel_3a emulator until the upgrade is done? |
Hi all, with the release of 3.13.1, can anyone check if they hit this issue when they try to upgrade? |
Just tried and no luck for me.
|
After
|
Facing the same problem. Solved with |
|
I did the following and it worked (credits for Lano): On the directory where Flutter is located:
Hope it works! |
|
Hi everyone, thanks for your responses. I am able to reproduce this same behaviour on the |
yes --force works but as reported earlier, there is a new bug which throws the reported error if you do not use --force, beyond this, the 3.13.0 came with other bugs yet to be resolved: (though resolved and merged to Master, it is yet to be in the stable, hope it is also tested: [https://github.com/firebase/flutterfire/pull/11514] |
I want to point out that this also happens with the upgrade from 3.13.1 to 3.13.2 logs
|
Same issue for upgrade from 3.13.1 to 3.13.2.
|
I have the same error
|
I have the same problem :( |
Ok, it's fine. I am not the only one who got the same problem. |
Same
|
For me the upgrade worked when running it in the flutter install directory. It appears to me that it fails when running the upgrade command in the directory of my flutter application when my flutter application has uncommitted files. |
Same issue when upgrading to 3.13.2. I'm pretty use I used
|
I had the same error when trying to upgrade to 3.13.2 from 3.13.0. @christoph-zenger-hcsg Thanks for the suggestion. Running |
|
Ahh, thanks for this clue! This whole time my current working directory when I run |
Still not working. Is this a problem in:
so to upgrade I do what exactly? |
Unfortunately you will need to either do a Also note, that I haven't cherrypicked the fix to stable yet. So even if you use the workaround today, you will still need to use the workaround for the next hotfix release to get the fix. |
Ok. It is what it is. Thank you for your attention |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
Edit by @christopherfujino This is a bug in the tool. Currently known safe workarounds to upgrade are to:
flutter doctor -v
), then runflutter upgrade
Two hotfixes are currently being worked on, however, users will still need to use these workarounds to get them:
A postmortem report on this is forthcoming.
Is there an existing issue for this?
Steps to reproduce
Run "flutter upgrade" on 3.13.0 stable
Actual results
I got this error:
Unknown flutter tag. Abandoning upgrade to avoid destroying local changes. It is recommended to use git directly if not working on an official channel.
Logs
No response
Flutter Doctor output
Doctor output
The text was updated successfully, but these errors were encountered: