Skip to content

Comments

Fix Diffuse workflow to use signed APK filename#405

Merged
hossain-khan merged 1 commit intomainfrom
fix/diffuse-workflow-apk-path
Dec 6, 2025
Merged

Fix Diffuse workflow to use signed APK filename#405
hossain-khan merged 1 commit intomainfrom
fix/diffuse-workflow-apk-path

Conversation

@hossain-khan
Copy link
Owner

Problem

The Diffuse workflow was failing because it was looking for app-release-unsigned.apk, but the build configuration produces a signed APK named app-release.apk.

Root Cause

In build.gradle.kts, the release build type has signing configured, which produces a signed APK instead of an unsigned one.

Solution

Updated all references in the Diffuse workflow from app-release-unsigned.apk to app-release.apk:

  • Base APK save path
  • Diffuse comparison new file path
  • PR APK upload artifact path

Testing

This fix will be validated when the workflow runs on this PR itself.

Related

Fixes the Diffuse workflow failures seen in recent PRs.

The workflow was looking for app-release-unsigned.apk, but since
the release build has signing configured, Gradle produces
app-release.apk (signed) instead.
@github-actions
Copy link

github-actions bot commented Dec 6, 2025

Code Coverage Report

View Coverage Report

@hossain-khan hossain-khan merged commit 5a9a896 into main Dec 6, 2025
4 checks passed
@hossain-khan hossain-khan deleted the fix/diffuse-workflow-apk-path branch December 6, 2025 13:59
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