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

Could not extract Flutter SDK, error: exit status 128 #17

Closed
wklimczyk opened this issue May 7, 2020 · 5 comments
Closed

Could not extract Flutter SDK, error: exit status 128 #17

wklimczyk opened this issue May 7, 2020 · 5 comments
Labels
bug Something isn't working

Comments

@wklimczyk
Copy link

wklimczyk commented May 7, 2020

We've set Flutter version to TAG 1.17.0
Flutter install when setting stable version to: 1.17.0
success

then
Flutter command with version set to: 1.17.0
pub get
Extracting Flutter SDK to /Users/vagrant/Library/flutter
Version 1.17.0 not found in releases, trying snapshot.
Could not extract Flutter SDK, error: exit status 128
| |
+---+---------------------------------------------------------------+----------+
| x | flutter@0 (exit code: 2)

The version exists
https://github.com/flutter/flutter/releases/tag/1.17.0
also here: https://flutter.dev/docs/development/tools/sdk/releases
also it's installed via Flutter install

@koral-- koral-- added the bug Something isn't working label May 7, 2020
@mateusfsilva
Copy link

Same with version 1.17.3

Extracting Flutter SDK to /opt/flutter
Version 1.17.3 not found in releases, trying snapshot.
Could not extract Flutter SDK, error: exit status 128

I think that is because of the name change from version 1.17.0 which does not has the v before the version number.

@koral--
Copy link
Member

koral-- commented Jun 25, 2020

Thanks @mateusfsilva!
Indeed, it seems that Google have removed v prefix starting from version 1.17.x.

I'll update the step ASAP.

@koral--
Copy link
Member

koral-- commented Jun 27, 2020

Fixed in 0.0.10 bitrise-io/bitrise-steplib#2571

@lukaszdebowski
Copy link

@koral-- Just FYI, I've had this issue where the Bitrise step could not be updated from version 0.0.9 to 0.0.10 using the "red arrow" button that usually updates the step to the latest version - it says that the latest is 0.0.9.

But if you add the step as a brand new step, then the version says it is 0.0.10 (even tho the "latest step version" still says 0.0.9).

Might wanna look into that, thanks for the update anyway 👍

@koral--
Copy link
Member

koral-- commented Jul 1, 2020

@lukaszdebowski it seems to be related to this change: https://blog.bitrise.io/new-options-for-locking-step-versions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants