Removing manual installation build tools 34.0.0 #1740
Merged
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.
Recent jobs on CI builds from AGP versions were failing with:
There is an initial workaround to fix this problem in PR #1720. The proposed solution is valid, but while trying to understand the reason for the failure, we observed that it is caused by an attempt to write to the Android folder during the build. This occurs in a folder created by a different user (root). The original folder is created when manually installing the SDK build tool version 34.0.0(during the gha setup):
Given this situation, we need to understand what caused this change in the GHA infrastructure: The ubuntu-latest workflows have started rolling out the ubuntu-24.04 image since December 5th (scheduled to be completed by January 17th). One of the changes in the new version is the use of SDK build tools version 34.0.0.
This PR removes the manual installation of the SDK tools (performed as root), resolving the folder permission issue caused by the user mismatch.