feat(Android, Tabs): Add special effects to bottom tabs on Android

[Ubax]

Description

Adds special effects to bottom tabs implementation on Android

Screen.Recording.2025-10-24.at.13.34.17.mov

Changes

1. Added ViewFinder helper, which has utils for finding ScrollView and Stack. The implementation is based on iOS one.
2. Added popToRoot method to ScreenStack. It dispatches dismiss event for every non-root active screen on Stack. It is JS responsibility to remove this screen from stack. This way the dismiss can be prevented.
3. Added handler for repeated tab press event.

Test code and steps to reproduce

Bottom tabs test app

Checklist

• Included code example that can be used to test this change
• Updated TS types
• Updated documentation:
  • https://github.com/software-mansion/react-native-screens/blob/main/guides/GUIDE_FOR_LIBRARY_AUTHORS.md
  • https://github.com/software-mansion/react-native-screens/blob/main/native-stack/README.md
  • https://github.com/software-mansion/react-native-screens/blob/main/src/types.tsx
  • https://github.com/software-mansion/react-native-screens/blob/main/src/native-stack/types.tsx
• Ensured that CI passes

[kkafar]

Looks good overall. Only thing I'm worried about is the dismiss model, where we first notify JS & just then dismiss the screens.

I haven't made my mind yet, whether I wanna go this way or not. Will be back soon with more feedback.

[kkafar]

Okay, so as we talked, I agree for current dismissal model, but it won't be stable. That is - it might be a subject of change in the future.

I'll revisit the code now & land it soon

[kkafar]

This does not work currently in TestBottomTabs example. For some reason the hierarchy looks as follows:

This causes stack to be not found by the "first descendant chain" algorithm.

This seems like rather common setup, therefore I need to investigate this first.

[kkafar]

FYI: The root cause here is SafeAreaListener recently added to react-navigation. I've started pushing changes to fix this there.