Fix Compose test host selection in release preflight - #36
Merged
Conversation
APK artifacts
Built from commit |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 0.1.0 release workflow failed before publishing artifacts because
testReleaseUnitTestcannot launch the Compose test host Activity:ui-test-manifestis intentionally a debug-only dependency.Run the complete JVM suite with
testDebugUnitTest, matching PR CI, before building the signed release APKs. Release packaging and signing remain unchanged, and test host Activities stay out of release artifacts.Validation: reproduced the missing-Activity failure locally with NavigationUiTest on the release variant; all 149 JVM tests pass on debug via Bundler/Fastlane.
bash -nandgit diff --checkpass.