-
Notifications
You must be signed in to change notification settings - Fork 70
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
Expand-Archive Fails #369
Comments
I'm also experiencing the same error. |
Hello, sorry for the extra late reply. From the log it seems like the error happens when trying to expand the zip file. Could you please check if it still happens with the current release? A bunch of node dependencies got updated, it might just solve it. If not, we'll have to look into it |
Just tried it with 3.0.0 and the problem persists unfortunately. |
Could you post the log?
…-------- Original Message --------
On Sep 25, 2023, 07:05, Laura wrote:
Just tried it with 3.0.0 and the problem persists unfortunately.
—
Reply to this email directly, [view it on GitHub](#369 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AAGGN6P7Y4NKHRFK35NDSGTX4D7HTANCNFSM6AAAAAASPGXJMA).
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Which powershell version do you have? I see this is a common issue
actions/runner#1883
actions/setup-go#241
…-------- Original Message --------
On Sep 25, 2023, 07:10, Laura wrote:
|
Also, once we solve this, you are going to run into the JDK 17 requirement. From your log I see you're still on JDK 8. See Readme.md on how to change the JDK
…-------- Original Message --------
On Sep 25, 2023, 07:21, Vilius Sutkus wrote:
Which powershell version do you have? I see this is a common issue
actions/runner#1883
actions/setup-go#241
-------- Original Message --------
On Sep 25, 2023, 07:10, Laura wrote:
|
Looks like it's version 5.1 which seems to ship with most Windows versions. I'll have to find an action to install PowerShell Core if I want my builds to be reproducible on other runner hosts. I'll let you know how it goes. |
For those also self-hosting on Windows and want a reproducible build, here's my steps to ensure PowerShell Core is installed before running setup-android. The exit code is ignored because it will return 1 if PowerShell Core is already installed. Since we're already using dotnet in our builds anyway, installing via dotnet was the easiest approach but there are other methods available. - name: Setup .NET Core
uses: actions/setup-dotnet@v3
with:
dotnet-version: 6.0.x
env:
DOTNET_INSTALL_DIR: ~/.dotnet
- name: Setup PowerShell Core
continue-on-error: true
run: dotnet tool install --global PowerShell
- name: Setup Android SDK
uses: android-actions/[email protected] This solves the issue for me so I hope it helps others as well. |
After updating the action version from 2.0.7 to 2.0.10 I get this error when running my build:
The YAML for this step is as follows:
The runner is self-hosted on Microsoft Windows Server 2019 Datacenter.
The text was updated successfully, but these errors were encountered: