From 187a568764f0fb5b933eb7a76b936313756338e3 Mon Sep 17 00:00:00 2001
From: MxKevinBeqo <kevin.beqo@mendix.com>
Date: Thu, 2 Jul 2026 13:20:06 +0200
Subject: [PATCH] fix: google policy issue with media permissions

---
 android/app/src/main/AndroidManifest.xml | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/android/app/src/main/AndroidManifest.xml b/android/app/src/main/AndroidManifest.xml
index e136e20..7de895d 100644
--- a/android/app/src/main/AndroidManifest.xml
+++ b/android/app/src/main/AndroidManifest.xml
@@ -37,10 +37,16 @@
     <!-- Ignore deprecation: We still need this for the RN I think -->
     <uses-permission android:name="android.permission.USE_FINGERPRINT"/>
     <uses-permission android:name="android.permission.USE_BIOMETRIC" />
-    <!-- Ignore deprecation -->
     <!-- Required for Android 13+ (SDK 33+) -->
-    <uses-permission android:name="android.permission.READ_MEDIA_IMAGES" android:minSdkVersion="33"/>
-    <uses-permission android:name="android.permission.READ_MEDIA_VIDEO" android:minSdkVersion="33"/>
+    <!--
+    READ_MEDIA_IMAGES and READ_MEDIA_VIDEO are explicitly removed (tools:node="remove") following
+    Google Play's Photo and Video Permissions policy.
+    These broad permissions are only allowed for apps whose core purpose is persistent media library access.
+    As a developer platform, Make It Native does not qualify; CameraRoll.getPhotos() enumeration will not
+    work on API 33+. Use tools:node="remove" to also block any dependency from re-adding them during manifest merge.
+    -->
+    <uses-permission android:name="android.permission.READ_MEDIA_IMAGES" tools:node="remove"/>
+    <uses-permission android:name="android.permission.READ_MEDIA_VIDEO" tools:node="remove"/>
     <uses-permission android:name="android.permission.READ_MEDIA_AUDIO" android:minSdkVersion="33"/>
     <uses-permission android:name="android.permission.READ_MEDIA_VISUAL_USER_SELECTED" android:minSdkVersion="33"/>