-
Notifications
You must be signed in to change notification settings - Fork 457
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 plugin breaks during precache #5258
Comments
Thank you for reporting your feedback to us! The internal ticket has been created: https://warthogs.atlassian.net/browse/CRAFT-4149.
|
Good day, is there any workaround for this issue in the meantime? I have tried building without the Flutter plugin and tried to do things manually on the override-build step but run into all sorts of errors during runtime. |
Hi @munch-software, unfortunately we don't have a workaround, but we're planning to fix this ASAP - it should be resolved this week. |
Relevant upstream issue: flutter/flutter#163198 |
Bug Description
Currently, the Flutter plugin installs Flutter using an undocumented git-based method, which breaks due to what appear to be some internal forks to
git
in Flutter:(note the last line especially)
The issue here is that we clone with
-b stable
, which means only thestable
branch is present locally. Cloning themaster
branch instead gets us further, but still fails due to what appears to be the Flutter repository using a placeholder "0.0.0" version in that branch.However, there is a Flutter snap, which does not appear to have any of these troubles.
We could, alternatively, rename the local remote
stable
tomaster
as a workaround.To Reproduce
Attempt to build anything with the Flutter plugin
Environment
Any version of Snapcraft
snapcraft.yaml
Relevant log output
:: + flutter precache --linux :: Woah! You appear to be trying to run flutter as root. :: We strongly recommend running the flutter tool without superuser privileges. :: / :: 📎 :: fatal: Not a valid object name origin/master
Additional context
No response
The text was updated successfully, but these errors were encountered: