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
I'm not sure why I am getting this error. I didn't think dx.jar was used in the signing. It seems as if dx.jar got removed in later versions of the build tools. Possibly related to #17212
This is the error:
##[error]Error: Failed find: ENOENT: no such file or directory, stat '/azagent/android-sdk/build-tools/34.0.0/lib/dx.jar'
Environment type (Please select at least one enviroment where you face this issue)
Self-Hosted
Microsoft Hosted
VMSS Pool
Container
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Debian, I am using Eclipse-temurin21-jdk image
Relevant log output
##[error]Error: Failed find: ENOENT: no such file or directory, stat '/azagent/android-sdk/build-tools/34.0.0/lib/dx.jar'
Full task logs with system.debug enabled
[REPLACE THIS WITH YOUR INFORMATION]
Repro steps
No response
The text was updated successfully, but these errors were encountered:
New issue checklist
Task name
AndroidSigning@3
Task version
3.246.1
Issue Description
I'm not sure why I am getting this error. I didn't think dx.jar was used in the signing. It seems as if dx.jar got removed in later versions of the build tools. Possibly related to #17212
This is the error:
##[error]Error: Failed find: ENOENT: no such file or directory, stat '/azagent/android-sdk/build-tools/34.0.0/lib/dx.jar'
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Debian, I am using Eclipse-temurin21-jdk image
Relevant log output
##[error]Error: Failed find: ENOENT: no such file or directory, stat '/azagent/android-sdk/build-tools/34.0.0/lib/dx.jar'
Full task logs with system.debug enabled
Repro steps
No response
The text was updated successfully, but these errors were encountered: