From b2e1613aa7190a6c211bd6a8dd8dad9cfde2e647 Mon Sep 17 00:00:00 2001
From: KARTHIKEYAN DURAIAMY
 <127922596+KarthiKeyan05046@users.noreply.github.com>
Date: Thu, 19 Feb 2026 22:13:54 +0530
Subject: [PATCH] fix: use startActivityPreview instead of startFragmentPreview
 to properly handle hardware back navigation

When using startFragmentPreview, pressing Android hardware back while in preview
causes React Navigation to pop the screen while native preview fragment remains open,
leading to broken UI state.

Using startActivityPreview isolates preview in its own Activity and fixes the issue.
---
 .../margelo/nitro/multipleimagepicker/MultipleImagePickerImp.kt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/android/src/main/java/com/margelo/nitro/multipleimagepicker/MultipleImagePickerImp.kt b/android/src/main/java/com/margelo/nitro/multipleimagepicker/MultipleImagePickerImp.kt
index cdd8ca7..8491830 100644
--- a/android/src/main/java/com/margelo/nitro/multipleimagepicker/MultipleImagePickerImp.kt
+++ b/android/src/main/java/com/margelo/nitro/multipleimagepicker/MultipleImagePickerImp.kt
@@ -334,7 +334,7 @@ class MultipleImagePickerImp(reactContext: ReactApplicationContext?) :
                     return true
                 }
             })
-            .startFragmentPreview(index, false, assets)
+            .startActivityPreview(index, false, assets)
     }