ReactNative v0.75.4 with new architecture android app is crashing

[sankar-gp]

Current behavior

ReactNative v0.75.4 with new architecture android app is crashing when I click back. But it's working in iOS and when I disable new arch it's working fine. Issue is only with newArchEnabled=true

Error Log:
Cannot remove child at index 1 from parent ViewGroup[1332], only 2 children in parent. Warning: childCount may be incorrect! null

Expected behavior

App should not crash when newArchEnabled=true

Reproduction

norepo

Platform

• Android
• iOS
• Web
• Windows
• MacOS

Packages

• @react-navigation/bottom-tabs
• @react-navigation/drawer
• @react-navigation/material-top-tabs
• @react-navigation/stack
• @react-navigation/native-stack
• react-native-tab-view

Environment

• [] I've removed the packages that I don't use

package	version
@react-navigation/native	6.1.18
@react-navigation/bottom-tabs	6.6.1
@react-navigation/material-top-tabs	6.6.14
@react-navigation/native-stack	6.11.0
react-native-screens	3.34.0
react-native-gesture-handler	2.20.0
react-native-tab-view	3.5.2
react-native-pager-view	6.4.1
react-native	0.75.4
node	>=18
npm or yarn	yarn@3.6.4

[github-actions]

Hey @sankar-gp! Thanks for opening the issue. It seems that the issue doesn't contain a link to a repro.

The best way to get attention to your issue is to provide an easy way for a developer to reproduce the issue.

You can provide a repro using any of the following:

• Expo Snack
• TypeScript Playground
• GitHub repo under your username

A snack link is preferred since it's the easiest way to both create and share a repro. If it's not possible to create a repro using a snack, link to a GitHub repo under your username is a good alternative. Don't link to a branch or specific file etc. as it won't be detected.

Try to keep the repro as small as possible by narrowing down the minimal amount of code needed to reproduce the issue. Don't link to your entire project or a project containing code unrelated to the issue. See "How to create a Minimal, Reproducible Example" for more information.

You can edit your original issue to include a link to the repro, or leave it as a comment. The issue will be closed automatically after a while if you don't provide a repro.

[github-actions]

Couldn't find version numbers for the following packages in the issue:

• @react-navigation/stack

Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3.

[sankar-gp]

Couldn't find version numbers for the following packages in the issue:

• @react-navigation/stack

Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3.

@react-navigation/native-stack | 6.11.0

[github-actions]

Hey! Thanks for opening the issue. Seems that this issue is related to react-native-screens library which is a dependency of React Navigation. Can you also post your issue in this repo so that it's notified to the maintainers of that library? This will help us fix the issue faster since it's upto the maintainers of that library to investigate it.

[spyshower]

@sankar-gp I have been encountering this problem for quite some time too. It's probably related to flatlists.

[sankar-gp]

@spyshower Do you have any fix?

[spyshower]

@sankar-gp Nope, I am still in development so I switched to scrollviews for now. I think they are working on a fix on the react-native-screens repo

[WKampel]

Same issue

[samtsai]

I think this might be the issue: software-mansion/react-native-screens#2341

[spyshower]

I think it was supposed to be fixed in react-native-screens beta 9 but I still encounter the issue on that version :(