Skip to content

fix: Empty array & null checks in handleTabNavigatorChange method fixes #6698#6700

Merged
piaskowyk merged 4 commits intosoftware-mansion:mainfrom
aymather:fix/tab-navigator-crash
Dec 4, 2024
Merged

fix: Empty array & null checks in handleTabNavigatorChange method fixes #6698#6700
piaskowyk merged 4 commits intosoftware-mansion:mainfrom
aymather:fix/tab-navigator-crash

Conversation

@aymather
Copy link
Contributor

Fixes: Shared Element Transition (Solution provided) #6698

Add safety checks in handleTabNavigatorChange to prevent crash

This fixes a crash that occurs when _disappearingScreens array is empty or
contains invalid objects by adding appropriate null checks and bounds checking.

The crash would occur when:

  • The _disappearingScreens array is empty
  • navTabScreen or its reactSuperview is null
  • targetScreen is null

App was crashing during shared element transition because of invalid array access.

Fixes #6698

@aymather
Copy link
Contributor Author

I fixed one of the errors, but I'm not quite sure how exactly to fix the other failing check? Can I get some guidance?

Copy link
Member

@piaskowyk piaskowyk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for reporting the issue and providing the fix! I really appreciate your commitment ❤️

@piaskowyk piaskowyk added this pull request to the merge queue Dec 4, 2024
Merged via the queue into software-mansion:main with commit 65e6190 Dec 4, 2024
@aymather aymather deleted the fix/tab-navigator-crash branch December 4, 2024 21:00
tomekzaw pushed a commit that referenced this pull request Dec 9, 2024
#6698 (#6700)

Fixes:  Shared Element Transition (Solution provided) #6698 

Add safety checks in handleTabNavigatorChange to prevent crash

This fixes a crash that occurs when _disappearingScreens array is empty
or
contains invalid objects by adding appropriate null checks and bounds
checking.

The crash would occur when:
- The _disappearingScreens array is empty
- navTabScreen or its reactSuperview is null
- targetScreen is null

App was crashing during shared element transition because of invalid
array access.

Fixes #6698

---------

Co-authored-by: Krzysztof Piaskowy <krzysztof.piaskowy@swmansion.com>
@tomekzaw tomekzaw mentioned this pull request Dec 9, 2024
tomekzaw pushed a commit that referenced this pull request Dec 9, 2024
#6698 (#6700)

Fixes:  Shared Element Transition (Solution provided) #6698 

Add safety checks in handleTabNavigatorChange to prevent crash

This fixes a crash that occurs when _disappearingScreens array is empty
or
contains invalid objects by adding appropriate null checks and bounds
checking.

The crash would occur when:
- The _disappearingScreens array is empty
- navTabScreen or its reactSuperview is null
- targetScreen is null

App was crashing during shared element transition because of invalid
array access.

Fixes #6698

---------

Co-authored-by: Krzysztof Piaskowy <krzysztof.piaskowy@swmansion.com>
tjzel pushed a commit that referenced this pull request Dec 13, 2024
#6698 (#6700)

Fixes:  Shared Element Transition (Solution provided) #6698 

Add safety checks in handleTabNavigatorChange to prevent crash

This fixes a crash that occurs when _disappearingScreens array is empty
or
contains invalid objects by adding appropriate null checks and bounds
checking.

The crash would occur when:
- The _disappearingScreens array is empty
- navTabScreen or its reactSuperview is null
- targetScreen is null

App was crashing during shared element transition because of invalid
array access.

Fixes #6698

---------

Co-authored-by: Krzysztof Piaskowy <krzysztof.piaskowy@swmansion.com>
tjzel pushed a commit that referenced this pull request Dec 13, 2024
#6698 (#6700)

Fixes:  Shared Element Transition (Solution provided) #6698 

Add safety checks in handleTabNavigatorChange to prevent crash

This fixes a crash that occurs when _disappearingScreens array is empty
or
contains invalid objects by adding appropriate null checks and bounds
checking.

The crash would occur when:
- The _disappearingScreens array is empty
- navTabScreen or its reactSuperview is null
- targetScreen is null

App was crashing during shared element transition because of invalid
array access.

Fixes #6698

---------

Co-authored-by: Krzysztof Piaskowy <krzysztof.piaskowy@swmansion.com>
tjzel pushed a commit that referenced this pull request Dec 13, 2024
#6698 (#6700)

Fixes:  Shared Element Transition (Solution provided) #6698 

Add safety checks in handleTabNavigatorChange to prevent crash

This fixes a crash that occurs when _disappearingScreens array is empty
or
contains invalid objects by adding appropriate null checks and bounds
checking.

The crash would occur when:
- The _disappearingScreens array is empty
- navTabScreen or its reactSuperview is null
- targetScreen is null

App was crashing during shared element transition because of invalid
array access.

Fixes #6698

---------

Co-authored-by: Krzysztof Piaskowy <krzysztof.piaskowy@swmansion.com>
r0h0gg6 pushed a commit to r0h0gg6/react-native-reanimated that referenced this pull request Jul 28, 2025
software-mansion#6698 (software-mansion#6700)

Fixes:  Shared Element Transition (Solution provided) software-mansion#6698 

Add safety checks in handleTabNavigatorChange to prevent crash

This fixes a crash that occurs when _disappearingScreens array is empty
or
contains invalid objects by adding appropriate null checks and bounds
checking.

The crash would occur when:
- The _disappearingScreens array is empty
- navTabScreen or its reactSuperview is null
- targetScreen is null

App was crashing during shared element transition because of invalid
array access.

Fixes software-mansion#6698

---------

Co-authored-by: Krzysztof Piaskowy <krzysztof.piaskowy@swmansion.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Shared Element Transition (Solution provided)

2 participants

Comments