AzureDevOps Android 管道 zipalign - 失败，退出代码为 1
AzureDevOps Android Pipeline zipalign - failed with exit code 1
我不确定发生了什么，我们在 Azure Devops 中用于构建的一切都很好。
但就在最近，我们的每个构建在 zipaligning 时都失败了......当使用 Android Studio IDE 时，APK zipaligns 和构建都很好，但它在 Azure Devops 管道中失败了。
这是 Azure 的 zipalign 的起点：
Starting: AndroidSigning
==============================================================================
Task : Android signing
Description : Sign and align Android APK files
Version : 3.176.0
Author : Microsoft Corporation
Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/build/android-signing
==============================================================================
"C:\Program Files (x86)\Android\android-sdk\build-tools.0.2\zipalign.exe" -v 4 D:\a\s\app\build\outputs\apk\release\app-release-unsigned.apk.unaligned D:\a\s\app\build\outputs\apk\release\app-release-unsigned.apk
Verifying alignment of D:\a\s\app\build\outputs\apk\release\app-release-unsigned.apk (4)...
最后是失败消息：
Verification FAILED
##[error]Error: The process 'C:\Program Files (x86)\Android\android-sdk\build-tools.0.2\zipalign.exe' failed with exit code 1
最后，这是我们管道 YAML 的上下文：
trigger:
- master
pool:
vmImage: 'windows-latest'
steps:
- task: Gradle@2
inputs:
workingDirectory: ''
gradleWrapperFile: 'gradlew'
gradleOptions: '-Xmx5120m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8'
publishJUnitResults: false
testResultsFiles: '**/TEST-*.xml'
tasks: 'assembleRelease'
- task: AndroidSigning@3
inputs:
apkFiles: '**/*.apk'
apksign: true
apksignerFile: C:\Program Files (x86)\Android\android-sdk\build-tools.0.2\apksigner.bat
apksignerKeystoreFile: 'keystore.jks'
apksignerKeystorePassword: '$(jarsignerKeystorePassword)'
apksignerKeystoreAlias: 'alias'
apksignerKeyPassword: '$(jarsignerKeyPassword)'
apksignerArguments: --out $(Build.SourcesDirectory)/app/build/outputs/apk/release/app.apk
zipalign: true
zipalignFile: C:\Program Files (x86)\Android\android-sdk\build-tools.0.2\zipalign.exe
如有任何帮助，我们将不胜感激！
编辑：
这是构建未能发布工件的调试日志，当设置为 AndroidSigning@2（jarsigner 而不是 apksigner）
2020-11-02T15:49:43.9428841Z ##[debug]Evaluating condition for step: 'PublishBuildArtifacts'
2020-11-02T15:49:43.9430851Z ##[debug]Evaluating: SucceededNode()
2020-11-02T15:49:43.9431429Z ##[debug]Evaluating SucceededNode:
2020-11-02T15:49:43.9432781Z ##[debug]=> True
2020-11-02T15:49:43.9433320Z ##[debug]Result: True
2020-11-02T15:49:43.9433928Z ##[section]Starting: PublishBuildArtifacts
2020-11-02T15:49:43.9558720Z ==============================================================================
2020-11-02T15:49:43.9559237Z Task : Publish build artifacts
2020-11-02T15:49:43.9559565Z Description : Publish build artifacts to Azure Pipelines or a Windows file share
2020-11-02T15:49:43.9559869Z Version : 1.158.3
2020-11-02T15:49:43.9560103Z Author : Microsoft Corporation
2020-11-02T15:49:43.9560457Z Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/publish-build-artifacts
2020-11-02T15:49:43.9560873Z ==============================================================================
2020-11-02T15:49:43.9627178Z ##[debug]Using node path: C:\agents.175.2\externals\node\bin\node.exe
2020-11-02T15:49:44.1659280Z ##[debug]agent.TempDirectory=D:\a\_temp
2020-11-02T15:49:44.1690792Z ##[debug]loading inputs and endpoints
2020-11-02T15:49:44.1701762Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_SYSTEMVSSCONNECTION_ACCESSTOKEN
2020-11-02T15:49:44.1714168Z ##[debug]loading ENDPOINT_AUTH_SCHEME_SYSTEMVSSCONNECTION
2020-11-02T15:49:44.1717582Z ##[debug]loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION
2020-11-02T15:49:44.1719830Z ##[debug]loading INPUT_ARTIFACTNAME
2020-11-02T15:49:44.1721291Z ##[debug]loading INPUT_ARTIFACTTYPE
2020-11-02T15:49:44.1722675Z ##[debug]loading INPUT_PARALLEL
2020-11-02T15:49:44.1723961Z ##[debug]loading INPUT_PARALLELCOUNT
2020-11-02T15:49:44.1725345Z ##[debug]loading INPUT_PATHTOPUBLISH
2020-11-02T15:49:44.1729968Z ##[debug]loading SECRET_JARSIGNERKEYPASSWORD
2020-11-02T15:49:44.1732034Z ##[debug]loading SECRET_JARSIGNERKEYSTOREPASSWORD
2020-11-02T15:49:44.1733774Z ##[debug]loading SECRET_SYSTEM_ACCESSTOKEN
2020-11-02T15:49:44.1739927Z ##[debug]loaded 11
2020-11-02T15:49:44.1753983Z ##[debug]Agent.ProxyUrl=undefined
2020-11-02T15:49:44.1755481Z ##[debug]Agent.CAInfo=undefined
2020-11-02T15:49:44.1756003Z ##[debug]Agent.ClientCert=undefined
2020-11-02T15:49:44.1756464Z ##[debug]Agent.SkipCertValidation=undefined
2020-11-02T15:49:44.1769886Z ##[debug]check path : D:\a\_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe.158.3\task.json
2020-11-02T15:49:44.1771713Z ##[debug]adding resource file: D:\a\_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe.158.3\task.json
2020-11-02T15:49:44.1772325Z ##[debug]system.culture=en-US
2020-11-02T15:49:44.1792494Z ##[debug]PathtoPublish=D:\a\a\app\build\outputs\apk\release\
2020-11-02T15:49:44.1793208Z ##[debug]check path : D:\a\a\app\build\outputs\apk\release\
2020-11-02T15:49:44.1821823Z ##[debug]task result: Failed
2020-11-02T15:49:44.1857082Z ##[error]Publishing build artifacts failed with an error: Not found PathtoPublish: D:\a\a\app\build\outputs\apk\release\
2020-11-02T15:49:44.1867823Z ##[debug]Processed: ##vso[task.issue type=error;]Publishing build artifacts failed with an error: Not found PathtoPublish: D:\a\a\app\build\outputs\apk\release\
2020-11-02T15:49:44.1869433Z ##[debug]Processed: ##vso[task.complete result=Failed;]Publishing build artifacts failed with an error: Not found PathtoPublish: D:\a\a\app\build\outputs\apk\release\
2020-11-02T15:49:44.1890809Z ##[section]Finishing: PublishBuildArtifacts
所以在 github azure pipelines 任务问题线程上反复讨论之后，我发现通过从 4.1.0+ 更改我的 Android gradle 插件（它在我的项目级别 gradle.settings 中为 4.1.1) 到 4.0.0，Azure 管道构建将成功完成。
Gradle 本身停留在 6.5 版本，但是 Android gradle 插件被设置为 4.0.0 以使其构建成功。
然后，另一个人在 Google 问题跟踪器上指出了这个话题：
https://issuetracker.google.com/issues/162117652
从最新的 Android gradle 插件 4.1.0+ 开始，似乎不再需要 zipalign。我猜 Android gradle 插件 4.1.0+ 已经对 apk 进行了 zipaligns，因此任何后续调用 zipalign 都会显示失败，因为它已经 zipaligned。
所以这里的最终解决方案是保留最新版本的 Android gradle 插件 (4.1.1) 并将我的 Azure 中的 zipalign: true 更改为 zipalign: false管道 Android正在签署@3 任务。
即使在管道中将 zipalign 设置为 false，您也可以通过 运行 以下内容检查以确认您的 APK 是否实际上是 zipaligned：
zipalign -c -v 4 /path/to/app-release.apk.
此命令不会尝试修改文件，只会验证 apk 中的压缩并显示验证是否成功（apk 已成功压缩对齐）。
我不确定发生了什么，我们在 Azure Devops 中用于构建的一切都很好。
但就在最近，我们的每个构建在 zipaligning 时都失败了......当使用 Android Studio IDE 时，APK zipaligns 和构建都很好，但它在 Azure Devops 管道中失败了。
这是 Azure 的 zipalign 的起点：
Starting: AndroidSigning
==============================================================================
Task : Android signing
Description : Sign and align Android APK files
Version : 3.176.0
Author : Microsoft Corporation
Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/build/android-signing
==============================================================================
"C:\Program Files (x86)\Android\android-sdk\build-tools.0.2\zipalign.exe" -v 4 D:\a\s\app\build\outputs\apk\release\app-release-unsigned.apk.unaligned D:\a\s\app\build\outputs\apk\release\app-release-unsigned.apk
Verifying alignment of D:\a\s\app\build\outputs\apk\release\app-release-unsigned.apk (4)...
最后是失败消息：
Verification FAILED
##[error]Error: The process 'C:\Program Files (x86)\Android\android-sdk\build-tools.0.2\zipalign.exe' failed with exit code 1
最后，这是我们管道 YAML 的上下文：
trigger:
- master
pool:
vmImage: 'windows-latest'
steps:
- task: Gradle@2
inputs:
workingDirectory: ''
gradleWrapperFile: 'gradlew'
gradleOptions: '-Xmx5120m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8'
publishJUnitResults: false
testResultsFiles: '**/TEST-*.xml'
tasks: 'assembleRelease'
- task: AndroidSigning@3
inputs:
apkFiles: '**/*.apk'
apksign: true
apksignerFile: C:\Program Files (x86)\Android\android-sdk\build-tools.0.2\apksigner.bat
apksignerKeystoreFile: 'keystore.jks'
apksignerKeystorePassword: '$(jarsignerKeystorePassword)'
apksignerKeystoreAlias: 'alias'
apksignerKeyPassword: '$(jarsignerKeyPassword)'
apksignerArguments: --out $(Build.SourcesDirectory)/app/build/outputs/apk/release/app.apk
zipalign: true
zipalignFile: C:\Program Files (x86)\Android\android-sdk\build-tools.0.2\zipalign.exe
如有任何帮助，我们将不胜感激！
编辑： 这是构建未能发布工件的调试日志，当设置为 AndroidSigning@2（jarsigner 而不是 apksigner）
2020-11-02T15:49:43.9428841Z ##[debug]Evaluating condition for step: 'PublishBuildArtifacts'
2020-11-02T15:49:43.9430851Z ##[debug]Evaluating: SucceededNode()
2020-11-02T15:49:43.9431429Z ##[debug]Evaluating SucceededNode:
2020-11-02T15:49:43.9432781Z ##[debug]=> True
2020-11-02T15:49:43.9433320Z ##[debug]Result: True
2020-11-02T15:49:43.9433928Z ##[section]Starting: PublishBuildArtifacts
2020-11-02T15:49:43.9558720Z ==============================================================================
2020-11-02T15:49:43.9559237Z Task : Publish build artifacts
2020-11-02T15:49:43.9559565Z Description : Publish build artifacts to Azure Pipelines or a Windows file share
2020-11-02T15:49:43.9559869Z Version : 1.158.3
2020-11-02T15:49:43.9560103Z Author : Microsoft Corporation
2020-11-02T15:49:43.9560457Z Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/publish-build-artifacts
2020-11-02T15:49:43.9560873Z ==============================================================================
2020-11-02T15:49:43.9627178Z ##[debug]Using node path: C:\agents.175.2\externals\node\bin\node.exe
2020-11-02T15:49:44.1659280Z ##[debug]agent.TempDirectory=D:\a\_temp
2020-11-02T15:49:44.1690792Z ##[debug]loading inputs and endpoints
2020-11-02T15:49:44.1701762Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_SYSTEMVSSCONNECTION_ACCESSTOKEN
2020-11-02T15:49:44.1714168Z ##[debug]loading ENDPOINT_AUTH_SCHEME_SYSTEMVSSCONNECTION
2020-11-02T15:49:44.1717582Z ##[debug]loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION
2020-11-02T15:49:44.1719830Z ##[debug]loading INPUT_ARTIFACTNAME
2020-11-02T15:49:44.1721291Z ##[debug]loading INPUT_ARTIFACTTYPE
2020-11-02T15:49:44.1722675Z ##[debug]loading INPUT_PARALLEL
2020-11-02T15:49:44.1723961Z ##[debug]loading INPUT_PARALLELCOUNT
2020-11-02T15:49:44.1725345Z ##[debug]loading INPUT_PATHTOPUBLISH
2020-11-02T15:49:44.1729968Z ##[debug]loading SECRET_JARSIGNERKEYPASSWORD
2020-11-02T15:49:44.1732034Z ##[debug]loading SECRET_JARSIGNERKEYSTOREPASSWORD
2020-11-02T15:49:44.1733774Z ##[debug]loading SECRET_SYSTEM_ACCESSTOKEN
2020-11-02T15:49:44.1739927Z ##[debug]loaded 11
2020-11-02T15:49:44.1753983Z ##[debug]Agent.ProxyUrl=undefined
2020-11-02T15:49:44.1755481Z ##[debug]Agent.CAInfo=undefined
2020-11-02T15:49:44.1756003Z ##[debug]Agent.ClientCert=undefined
2020-11-02T15:49:44.1756464Z ##[debug]Agent.SkipCertValidation=undefined
2020-11-02T15:49:44.1769886Z ##[debug]check path : D:\a\_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe.158.3\task.json
2020-11-02T15:49:44.1771713Z ##[debug]adding resource file: D:\a\_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe.158.3\task.json
2020-11-02T15:49:44.1772325Z ##[debug]system.culture=en-US
2020-11-02T15:49:44.1792494Z ##[debug]PathtoPublish=D:\a\a\app\build\outputs\apk\release\
2020-11-02T15:49:44.1793208Z ##[debug]check path : D:\a\a\app\build\outputs\apk\release\
2020-11-02T15:49:44.1821823Z ##[debug]task result: Failed
2020-11-02T15:49:44.1857082Z ##[error]Publishing build artifacts failed with an error: Not found PathtoPublish: D:\a\a\app\build\outputs\apk\release\
2020-11-02T15:49:44.1867823Z ##[debug]Processed: ##vso[task.issue type=error;]Publishing build artifacts failed with an error: Not found PathtoPublish: D:\a\a\app\build\outputs\apk\release\
2020-11-02T15:49:44.1869433Z ##[debug]Processed: ##vso[task.complete result=Failed;]Publishing build artifacts failed with an error: Not found PathtoPublish: D:\a\a\app\build\outputs\apk\release\
2020-11-02T15:49:44.1890809Z ##[section]Finishing: PublishBuildArtifacts
所以在 github azure pipelines 任务问题线程上反复讨论之后，我发现通过从 4.1.0+ 更改我的 Android gradle 插件（它在我的项目级别 gradle.settings 中为 4.1.1) 到 4.0.0，Azure 管道构建将成功完成。
Gradle 本身停留在 6.5 版本，但是 Android gradle 插件被设置为 4.0.0 以使其构建成功。
然后，另一个人在 Google 问题跟踪器上指出了这个话题： https://issuetracker.google.com/issues/162117652
从最新的 Android gradle 插件 4.1.0+ 开始，似乎不再需要 zipalign。我猜 Android gradle 插件 4.1.0+ 已经对 apk 进行了 zipaligns，因此任何后续调用 zipalign 都会显示失败，因为它已经 zipaligned。
所以这里的最终解决方案是保留最新版本的 Android gradle 插件 (4.1.1) 并将我的 Azure 中的 zipalign: true 更改为 zipalign: false管道 Android正在签署@3 任务。
即使在管道中将 zipalign 设置为 false，您也可以通过 运行 以下内容检查以确认您的 APK 是否实际上是 zipaligned：
zipalign -c -v 4 /path/to/app-release.apk.
此命令不会尝试修改文件，只会验证 apk 中的压缩并显示验证是否成功（apk 已成功压缩对齐）。