You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since yesterday, I'm seeing this behavior every time I try to run a flutter upgrade
~/Code/flutter/examples/flutter_gallery[master*] $ flutter upgrade
Downloading package sky_engine... 712ms
Running 'flutter packages get' in sky_engine... 498ms
Building Dart SDK summary... 1779ms
Downloading engine artifacts android-arm... 2445ms
Downloading engine artifacts android-arm-profile... 2273ms
Downloading engine artifacts android-arm-release... 1882ms
Downloading engine artifacts android-x64... 1488ms
Downloading engine artifacts android-x86... 1440ms
Downloading engine artifacts ios...
Download failed: https://storage.googleapis.com/flutter_infra/flutter/e54b0e286ba7e07dcc32d12d8c68f6ca45cdbdf7/ios/artifacts.zip
because (404) Not Found
If this problem persists, please report the problem at
https://github.com/flutter/flutter/issues/new
Talking to @eseidelGoogle we think the issue is: when starting flutter upgrade, instead of updating the git repo, it's downloading assets. But, because the git repo is never updated, my version is stuck.
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 flutter doctor -v and a minimal reproduction of the issue.
Activity
sethladd commentedon Nov 3, 2016
cc @danrubel
Maybe we can always update the git repo as the first action when the user initiates a
flutter upgrade?For those following along, if you are stuck to, a workaround is:
Hixie commentedon Nov 21, 2017
This would be solved by fixing #6491.
Default locales test for flutter tester. Roll engine 162b2e9..7be0217 (…
Default locales test for flutter tester. Roll engine 162b2e9..7be0217 (…
github-actions commentedon Sep 4, 2021
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
flutter doctor -vand a minimal reproduction of the issue.