Repository navigation
Remove unused media permissions and bump to 3.5.3 - #23
Merged
Merged
Conversation
Google Play rejects the bundle under the Photo and Video Permissions policy because the manifest declared READ_MEDIA_IMAGES, READ_MEDIA_VIDEO and READ_MEDIA_AUDIO. The app never requests them: import and export use the Storage Access Framework and invoice sharing uses cacheDir with a FileProvider. Drop the three permissions, remove the WRITE_EXTERNAL_STORAGE prompts that gated export and share, request only CAMERA at dashboard start, and trim FileUtils to the two methods still in use.
setup-android v3 installs the removed 'tools' SDK package and fails with "Failed to find package 'tools'". v4 drops it and runs on Node 24. Bump checkout, setup-java and action-gh-release to their Node 24 majors and pin the runner to ubuntu-24.04 ahead of the ubuntu-latest migration.
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.
Summary
Google Play rejects the AAB under the Photo and Video Permissions policy because the manifest declared
READ_MEDIA_IMAGES,READ_MEDIA_VIDEOandREAD_MEDIA_AUDIO. The manifest merger report shows all three come from the app manifest, not from any library. The app never requests them: import and export use the Storage Access Framework and invoice sharing usescacheDirwith a FileProvider.WRITE_EXTERNAL_STORAGEprompts before export and invoice share (SAF and FileProvider need no storage permission on any API level)CAMERAat dashboard start; import flows on API < 29 still request storage at use timeFileUtils.javatotrimCacheandgetAvailableSpaceInKB, the only members referencedTest plan