Repository navigation
Fix Android SDK setup in CI - #42
Merged
Merged
Conversation
The v3 setup action still defaults to the removed tools package, so sdkmanager fails before unit tests run. Request platform-tools explicitly.
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
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.
Concern addressed: CI fails during Android SDK setup before unit tests run.
What changed and why: Explicitly request
platform-toolsfromsetup-android@v3. Its default also requests the removedtoolspackage, whichsdkmanagernow rejects.Evidence: The failed job reports
Warning: Failed to find package 'tools'. The v3 action declarestools platform-toolsas its default package list.git diff --checkpassed. The PR's GitHub Actions run will verify the setup and unit tests on the runner.Not in this PR: App detail UI changes are in PR #41.