fix(android): isolate Hands file provider#315
Merged
Conversation
Signed-off-by: Mobile QA Sentinel <raft-mobile-qa-sentinel@mail.build>
bytemain
added a commit
that referenced
this pull request
Jul 18, 2026
…er comment fix (#316) - README: document the native-symbols Maven classifier (zip layout, manifest, Build ID verification, fail-closed rule), incl. the same-channel requirement — JitPack and GitHub Packages builds of one tag have different Build IDs, so AAR and classifier must not be mixed. - symbolication-matrix: record Android native-symbols provenance (decision 0) — stripped AAR .so makes app-build intermediates fake symbols; SDK ships real symbols as the per-version classifier. - AndroidManifest: replace the stale 'authority namespaced so it never collides' comment — merger keys on android:name; the HandsFileProvider subclass (#315) is what avoids the collision. Co-authored-by: Quinn Rafferty <quinn.rafferty@hands.build>
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.
Problem
Android manifest merger identifies providers by
android:name. SDK 0.11.1 declaresandroidx.core.content.FileProvider, which collides with any host app that already declares the standard FileProvider class even when authorities differ. Raft therefore cannot consume 0.11.1.Changes
HandsFileProvider : FileProvidersubclass.${applicationId}.hands.fileproviderandhands_file_paths.Follow-up
Publish tag
android-sdk-v0.11.2after merge. Mobile PR #1267 already targets 0.11.2 and retains its own standard FileProvider without manifest overrides.Testing
publishReleasePublicationToMavenLocal -PVERSION_NAME=0.11.2passed with AAR and native-symbol classifier.:androidApp:processDebugMainManifestpassed against local SDK 0.11.2; both provider classes/authorities coexist withouttools:replace.:androidApp:copyHandsNativeSymbolspassed for 0.11.2.git diff --checkpassed.Need help on this PR? Tag
/codesmithwith what you need. Autofix is disabled.