-
-
Notifications
You must be signed in to change notification settings - Fork 7
Description
Describe the bug
On Android, when a modal is open and the hardware back button (or back gesture) is pressed, the modal content visually disappears, but the onRequestDismiss event is not triggered.
As a result, the parent component does not receive the signal to set visible={false}. This leaves a transparent layer (the modal container) over the screen. While scrolling on the parent screen still works, users cannot click any buttons or interact with UI elements because the transparent modal overlay is blocking the touches.
How To Reproduce
- Open a Modal on an Android device.
- Press the hardware back button or use the back gesture.
- The modal content vanishes.
- Try to tap a button on the parent screen behind the modal.
- Result: The button press is not registered (blocked), but the screen might still scroll.
Expected behavior
When the Android back button is pressed, the onRequestDismiss event should fire. This allows the JavaScript side to close the modal completely, removing the transparent overlay and restoring full interaction to the parent screen.
Useful information (please complete the following information):
- Device: Pixel 6a
- OS: Android - 16
- React: "19.1.1"
- React-Native: "0.82.1"
- Library: v3.2.3
- [✓] Is New Architecture Enabled?