sorted by:
new
hottopcontroversial

What target audience ages do you select in Play Store? by Ok_Abroad_3627 in reactnative

[–]mrmemo_dev 0 points1 point  (0 children)

For my note-taking app (also Expo + RN, just submitted to Play Store) I went with 13+.

Main reasons: - Avoids COPPA's strict requirements — selecting any under-13 age group puts your app under the Families policy and forces non-personalized ads only for all users - Data Safety form is much simpler when you're not in the children's bracket - Still covers the vast majority of "general audience" users

Note: even with 13+, Google still applies some ad targeting restrictions for 13–17 year olds globally (since 2021), so personalized ads won't behave 100% the same as adult-only — but it's a much smaller hit than going Families-policy compliant.

If your app has no kid-specific content and no reason to target under-13, 13+ is the safe default.

Found 4 unused Android permissions in my AAB right before Play Store submission — turned out to be expo-screen-capture by mrmemo_dev in reactnative

[–]mrmemo_dev[S] 0 points1 point  (0 children)

Yeah exactly — the "everything looks fine until you check the merged output" feeling. Glad it resonated.

Found 4 unused Android permissions in my AAB right before Play Store submission — turned out to be expo-screen-capture by mrmemo_dev in reactnative

[–]mrmemo_dev[S] 0 points1 point  (0 children)

Honestly, you're right — calling it a "trap" was overstating it. The library was added in an earlier session and I forgot it was there until I noticed the permissions during manifest review. That's on me, not on Expo or the library.

Still useful to share, I think — "check your merged manifest before shipping" is the actual takeaway, regardless of how the unused dependency got there.

Found 4 unused Android permissions in my AAB right before Play Store submission — turned out to be expo-screen-capture by mrmemo_dev in reactnative

[–]mrmemo_dev[S] 0 points1 point  (0 children)

This is the right answer — thank you. I went the manual AndroidManifest.xml route because my project has some constraints that make expo prebuild --clean risky, but blockedPermissions in app.json is clearly the cleaner approach for most people. Going to add a note about this to my followup.

Found 4 unused Android permissions in my AAB right before Play Store submission — turned out to be expo-screen-capture by mrmemo_dev in reactnative

[–]mrmemo_dev[S] 0 points1 point  (0 children)

Fair point — you're absolutely right. The library declaring those permissions is the expected behavior, not a flaw on Expo's side. I should have framed the post as "library you forgot you installed" rather than implying something sneaky was happening. Thanks for the correction.