feat(flatpak): reconstruct standard maven filenames from local Gradle cache#5538
Merged
jamesarich merged 1 commit intoMay 20, 2026
Merged
Conversation
c2ca2a3 to
69f73a0
Compare
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.
Overview
This PR builds on top of the native Flatpak cache scanner (#5533) by introducing standard Maven filename reconstruction to prevent 404 download errors on non-standard cached files (such as
animation.aar).🛠️ Detailed Changes
Standard Maven Filename Reconstruction
~/.gradle/caches/modules-2/files-2.1), we occasionally encounter artifacts cached with a simplified filename that doesn't include the standard maven artifact coordinate metadata (for example,animation.aarinstead ofanimation-android-1.10.0.aar). In the Flathub sandbox build environment, attempting to download directly using the non-standard filename results in a 404 error from public repositories (such as Google Maven or Maven Central) because the remote servers only recognize the fully qualified coordinate-based filename.GenerateFlatpakSourcesTask:filenamestarts with the standard Maven$name-$versionpattern.$name-$version.$ext).serverFilename) for both the remote URL path construction and the finaldest-filenamemapping.🧪 Verification & Results
Spotless & Detekt Compliance
All project formatting and static analysis checks pass cleanly without a single lint regression: