Skip to content

Fix release publishing when mapping file is absent - #4

Open
aShanki wants to merge 1 commit into
masterfrom
fix/release-optional-mapping
Open

aShanki wants to merge 1 commit into
masterfrom
fix/release-optional-mapping

Conversation

@aShanki

@aShanki aShanki commented Sep 26, 2026

Copy link
Copy Markdown
Member

The v0.3.1 tag built and verified a signed APK, but the publish job failed while copying app/build/outputs/mapping/release/mapping.txt. Release minification is disabled, so no mapping file is generated.

Copy mapping.txt only when it exists. The APK and checksum remain required. I exercised the workflow's actual asset step with a test APK and no mapping file; it produced the APK and SHA256SUMS.txt successfully.

The v0.3.1 prerelease was published manually from the successful signed CI artifact and its public checksum was verified. This PR fixes future tag releases.

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.

1 participant