Touch events blocked after dismissModal on iOS + dismissModal animation options not respected

[viper4595]

What happened?

When using showModal / dismissModal from react-native-navigation on iOS, there appears to be a delay after calling dismissModal during which touch events are blocked. During this short period, the UI becomes unresponsive and prevents triggering another showModal (or any touch interaction).

Additionally, the animation configuration for dismissModal does not seem to be applied correctly, even though similar settings for showModal work as expected.

Actual Behavior
After dismissModal, touch interactions are blocked briefly (~a few hundred ms).
Attempting to open another modal immediately fails due to unresponsive UI.
dismissModal animation config appears to be ignored.
In contrast, disabling animation for showModal works correctly.

  animations: {
    showModal: {
      enabled: false,
      enter: {
        enabled: false,
      },
      exit: {
        enabled: false,
      },
    },
    dismissModal: {
      enabled: false,
      enter: {
        enabled: false,
      },
      exit: {
        enabled: false
      },
    },
  },
}

What was the expected behaviour?

• After calling dismissModal, the UI should immediately be interactive.
• Touch events should not be blocked.
• dismissModal animation options should be respected (e.g. disabling animation or customizing duration).

Was it tested on latest react-native-navigation?

• I have tested this issue on the latest react-native-navigation release and it still reproduces.

Help us reproduce this issue!

• Press a button to call Navigation.showModal().
• Press a button to call Navigation.dismissModal().
• Press a button to call Navigation.showModal() again not working for a while

In what environment did this happen?

React Native Navigation version: 8.7.5
React Native version: 0.84.1
Has Fabric (React Native's new rendering system) enabled: (yes/no) yes
Node version: 22
Device model: iPhone 17 Pro simulator
iOS version: 26.3

[markdevocht]

@viper4595 is this bug still reproduced in RNN 8.8.2?

[viper4595]

@viper4595 is this bug still reproduced in RNN 8.8.2?

Yes, I tried it on RN 8.8.2 and the result is the same