Skip to content

fix(vivo): upload the signed vivo APK on its own, with a readable name - #2690

Closed
cuong-tran wants to merge 1 commit into
maxrave-dev:devfrom
cuong-tran:fix/vivo-apk-artifacts
Closed

cuong-tran wants to merge 1 commit into
maxrave-dev:devfrom
cuong-tran:fix/vivo-apk-artifacts

Conversation

@cuong-tran

Copy link
Copy Markdown
Contributor

The release job uploaded vivoAndroidApp/build/outputs/apk/release/*.apk, which zipped the unsigned APK that build_and_sign_apk.sh leaves behind together with the signed one. The nightly zipped its one APK under the name vivoAndroidApp-release-unsigned-signed.apk.

Both jobs now copy the single signed APK to SimpMusic--[nightly--]full-vivo-arm64-v8a.apk and upload it with upload-artifact@v7 and archive: false, so it downloads as the APK itself instead of a zip. The step fails unless it finds exactly one signed APK.

The release job uploaded vivoAndroidApp/build/outputs/apk/release/*.apk, which zipped the unsigned APK that build_and_sign_apk.sh leaves behind together with the signed one. The nightly zipped its one APK under the name vivoAndroidApp-release-unsigned-signed.apk.

Both jobs now copy the single signed APK to SimpMusic-<version>-[nightly-<sha>-]full-vivo-arm64-v8a.apk and upload it with upload-artifact@v7 and archive: false, so it downloads as the APK itself instead of a zip. The step fails unless it finds exactly one signed APK.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants