App Store / Google Play · 清单验收 · 不承诺过审Telegram @hagee66

上架通

GOEE LISTING LEDGER

№ ENgoee.cc
账号归你 · 邀请协作


2026-02-16

Play photos and video permissions: scope and declarations

After media permission tightening: how to declare and alternatives when you truly need library access. Telegram @hagee66.

This guide · Guide library · Apple listing · Google listing · Both stores · Telegram @hagee66

From Android 13, split media permissions and Play policy forms for photos/video access ended the “READ_EXTERNAL_STORAGE for everything” era. Tool, social, and scanner apps still declare broad read access, or Data Safety says “no photo upload” while SDKs read metadata. Review compares manifest, runtime requests, store declarations, privacy policy.

Inventory with Android permission declaration and privacy labels. APIs like Photo Picker per Android and Play docs. No approval promise.

What this guide solves

  • “Pick one image” but broad media read declared.
  • Camera-only crop page yet video read in manifest.
  • Console “yes” for photos/video but no matching feature in app.
  • Photo Picker used but full-library read still declared—policy email.
  • Google Play materials say “local only” but cloud upload.
  • Rejection to downgrade—can picker satisfy product?

Who should read

  • Android eng: manifest, targetSdk, runtime, picker integration.
  • Product: “pick one” vs “scan whole library.”
  • Listing/compliance: Play forms, Data Safety, description.
  • Permission rejection teams: common rejection codes.

Core practice

1. Must you read the library?

Scenario Prefer
Avatar, single upload Photo Picker / SAF—minimal read
Bulk backup Explicit read + policy + user value
Camera only CAMERA—not whole library
Edit one picked file Single URI grant

Official APIs; test on production targetSdk device.

2. Minimize manifest

  • Remove unused READ_MEDIA_* / legacy storage.
  • Gradle merged manifest from dependencies—upgrade or swap libs.
  • SDK disclosure—ads/analytics reading media?

3. Play Console declaration

Photo/video questionnaire (names change) asks core use, frequency, upload. Must match:

  • In-app feature;
  • Data Safety photo/video types;
  • Privacy policy album section.

Contradictions increase reject risk. Walk store description → app → pick image before filling.

4. Runtime UX

5. Store creative

“Smart album organize” in screenshots → tappable in build—or metadata reject fix. Don’t claim “we don’t read photos” with read permissions.

6. After rejection

  1. Copy cited permissions and policy links.
  2. Manifest + merge list provenance.
  3. Picker if possible; else update forms/policy + notes with user path.
  4. New build—rejection fix.

7. Cross-platform alignment

iOS permission strings say “organize album” while Android declares full read—users and review cross-compare. Shared media data flow: pick → edit → upload? → retention—one master doc for policy, Data Safety, nutrition labels.

Picker on Android but full PHPhotoLibrary on iOS—explain in product copy, not vague “access photos to serve you.”

8. 15-minute pre-submit

  • Fresh install deny → main path.
  • Fresh install allow → pick path.
  • Verify merged permissions (toolchain commands evolve).
  • Release-signed package—not debug with extra deps.

9. Feature graphic and video

Graphic/video showing “smart album” without read permission and no button—same as metadata reject fix. Fix Google Play materials and build—not permissions only. Internal vs production manifest: install both flavors; compare Settings permission list.

Copy-paste template

[Play media permission inventory]
targetSdk:
Declared permissions:
First trigger UI per permission:
Photo Picker / SAF: Y/N
Upload to server: Y/N (Data Safety if yes)
Console questionnaire screenshot date:
Privacy policy section:
SDK media read (name / doc):
Store mentions album: Y/N
Deny fallback path:
Test device + Android version:
Build:

Common mistakes

  1. Copy competitor manifest list.
  2. Debug-only permission test; release merge bigger.
  3. Data Safety “not collected” + READ_MEDIA_IMAGES.
  4. “Compatibility” storage on targetSdk 34+.
  5. Notes omit how to trigger pick.
  6. iOS/Android policy paragraph mixed wrong.
  7. “Request first ask later” like SMS call log.

FAQ

Pick one image—Data Safety photos?
If data leaves device or persistent read—usually declare; single picker URI no upload—official Data Safety defs; when unsure, match facts.

Editor SDK reads library—who owns?
Integrator manifests and declares; min-permission config or change SDK.

Upgraded users old grants?
targetSdk may change behavior—test upgrade path in release notes.

Android stricter affects iOS?
Not directly—but privacy labels narrative should match.

“Not core” but feature in submenu?
May still fail—tighten declaration or surface entry so “core” is clear.

Next steps

Related reading

Back to guide library · Telegram @hagee66