[Android] Crash in removeViewAt ("Unable to find parentView for tag") when a view is flattened in the commit right after it mounts
Maintainers usually reply within 2 days
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Read the linked fix in pull request #60019 and trace the reported mount sequence around maybePreallocateShadowNode, executeMount, and Android view preallocation. The issue includes a reproducer and logs; use them to check the race and whether the proposed fix prevents it. Done means the release build no longer crashes through the reported sequence.
Written by the indexing model from the issue text.
Description
Description
After moving to 0.88.1 our Android release build started crashing now and then with Unable to find parentView for tag 1878 from SurfaceMountingManager.removeViewAt. Right before the crash there are a few soft exceptions like Unable to find viewState for tag: [1878] for addViewAt. I think this is the same crash as #58526.
I turned on enableFabricLogs and followed the tag through the mount items. It's a race between view preallocation and executeMount:
- A View is created in a small update, so
maybePreallocateShadowNodequeues it. - The first commit has the View with
opacity, so it's a real view.executeMountsendsCREATEand adds the tag toallocatedViewTags. - A layout effect flattens it again in a second commit, same JS task.
executeMountsendsDELETEand erases the tag. - Only now the UI thread drains the queue. The tag isn't in
allocatedViewTagsanymore, so it gets added back and preallocated in Java, and theDELETEthat is already queued removes that Java view. On the C++ side the tag stays allocated, with nothing behind it. - The next time the same view turns into a real view, its
CREATEis skipped because the tag looks allocated.INSERTgoes into a view that doesn't exist (the soft exceptions), andUPDATE EVENTEMITTERleaves the placeholderViewStatefrom #58526. - When it's flattened again,
REMOVEfrom that placeholder throws.
With disableViewPreallocationAndroid the crash is gone. In our app it was the copy button of a code row: the wrapper gets opacity when the code expires and loses it when the next code comes in.
I have a fix that skips preallocation for families that are already part of a committed tree: #60019
Steps to reproduce
- Clone the reproducer below.
cd ReproducerApp/android && ./gradlew assembleRelease, install the APK.- Open the app. It closes within a few seconds (5 out of 5 launches on an API 36 emulator, between 4 and 18 seconds).
The repro mounts a new wrapper every 1.5 s, flattens it in a layout effect, then gives it opacity again after 400 ms and takes it away after 800 ms.
React Native Version
0.88.1
Affected Platforms
Runtime - Android
Output of npx @react-native-community/cli info
System:
OS: macOS 26.6.2
CPU: (14) arm64 Apple M3 Max
Memory: 259.25 MB / 36.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 22.22.2
Yarn:
version: 1.22.22
npm:
version: 10.9.7
Watchman:
version: 2025.12.15.00
IDEs:
Android Studio: 2025.1 AI-251.25410.109.2511.13752376
Xcode:
version: 26.5/17F42
Languages:
Java:
version: 17.0.20.1
npmPackages:
"@react-native-community/cli":
installed: 20.2.0
wanted: 20.2.0
react:
installed: 19.3.0
wanted: 19.3.0
react-native:
installed: 0.88.1
wanted: 0.88.1
Android:
hermesEnabled: true
newArchEnabled: true
Stacktrace or Logs
dispatchPreMountItems: PreAllocateViewMountItem [1878] - component: RCTView surfaceId: 21 isLayoutable: true
Executing mountItem: CREATE [1878] - layoutable:1 - RCTView
Executing mountItem: INSERT [1876]->[1878] @0
Executing mountItem: INSERT [1878]->[634] @4
...
Executing mountItem: REMOVE [1876]->[1878] @0
Executing mountItem: REMOVE [1878]->[634] @4
Executing mountItem: DELETE [1878]
-- 52 s later, no CREATE for 1878 --
Executing mountItem: INSERT [1878]->[634] @4
Executing mountItem: INSERT [1876]->[1878] @0
Executing mountItem: UPDATE EVENTEMITTER [1878]
ReactNoCrashSoftException: Unable to find viewState for tag: [1878] for addViewAt
Executing mountItem: REMOVE [1876]->[1878] @0
java.lang.IllegalStateException: Unable to find parentView for tag 1878
at com.facebook.react.fabric.mounting.SurfaceMountingManager.removeViewAt(SurfaceMountingManager.kt)
at com.facebook.react.fabric.mounting.mountitems.IntBufferBatchMountItem.execute(IntBufferBatchMountItem.kt)
at com.facebook.react.fabric.mounting.MountItemDispatcher.executeOrEnqueue(MountItemDispatcher.kt)
at com.facebook.react.fabric.mounting.MountItemDispatcher.dispatchMountItems(MountItemDispatcher.kt)
at com.facebook.react.fabric.mounting.MountItemDispatcher.tryDispatchMountItems(MountItemDispatcher.kt)
at com.facebook.react.fabric.FabricUIManager$DispatchUIFrameCallback.doFrameGuarded(FabricUIManager.java)
MANDATORY Reproducer
- Dominant language
- C++
- Stars
- 127k
- Forks
- 25.5k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 235
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from react/react-native
-
Needs: Author Feedback Needs: Repro
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
react/react-native#60059 · 1 comment ·
Maintainers usually reply within 2 days
-
Needs: Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
react/react-native#60000 ·
Maintainers usually reply within 2 days
-
`yarn test-ios` exits before building RNTester: `objc-test.sh` launches the WebSocket server script #59433 deletedPossibly taken @lazerg claimed this 4 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
react/react-native#59939 ·
Maintainers usually reply within 2 days
-
iOS Fabric pointer-handler reset leaves the next lone touch non-primaryPossibly taken @alleneubank claimed this 6 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
react/react-native#59919 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
react/react-native#59722 ·
Maintainers usually reply within 2 days
All issues in react/react-native
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
petercorke/robotics-toolbox-python#943 · 1 comment ·
Maintainers usually reply within 1 day
-
area:build bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
NatronGitHub/openfx-arena#71 ·
Maintainers usually reply within 1 day
-
upstream-blocked
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ROCm/FastFlowLM#1057 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
NatronGitHub/openfx-gmic#45 ·
Maintainers usually reply within 1 day