Skip to content

[Due for payment 2026-10-02] [$250] [Sentry: APP-7AR / APP-H7A] HybridApp Android Fabric mount crash — addViewAt/removeViewAt on clipping views #98791

Closed

Description

@mountiny

Sentry

Both are Fabric mount-item failures on the Android HybridApp, filed together because they share the same root cause: a mount instruction is applied to a view tree that no longer matches the shadow tree it was computed against.

Impact (snapshot at filing, 2026-08-17)

Sentry ID Users (last 14d) Users (total since first seen) Events First seen
APP-7AR 63 86 132 2026-03-11
APP-H7A 25 29 29 2026-07-07
  • Last seen: ongoing (both fired within the last hour at filing time)
  • Platform: Android, HybridApp (org.me.mobiexpensifyg)
  • App version(s): 9.4.52-11, 9.4.53-x, 9.4.54-1
  • Affected view(s): TabNavigator, Inbox
  • Mechanism: chained / UncaughtExceptionHandler, level fatal
  • Devices: not device-specific — reproduced on Samsung SM-S942B (Android 16) and SM-F936B (Android 14), across device.class: high

Stack trace (top frames)

APP-7AR — insert path

com.facebook.react.fabric.FabricUIManager$DispatchUIFrameCallback.doFrameGuarded(FabricUIManager.java:1664)
com.facebook.react.fabric.mounting.MountItemDispatcher.dispatchMountItems(MountItemDispatcher.kt:250)
com.facebook.react.fabric.mounting.mountitems.IntBufferBatchMountItem.execute(IntBufferBatchMountItem.kt:122)
com.facebook.react.fabric.mounting.SurfaceMountingManager.addViewAt(SurfaceMountingManager.kt:382)
com.facebook.react.views.view.ReactClippingViewManager.addView(ReactClippingViewManager.kt:36)
android.view.ViewGroup.addViewInner(ViewGroup.java:5648)
android.view.ViewGroup.addInArray(ViewGroup.java:5767)

Underlying throw: IndexOutOfBoundsException: index=1 count=0, rethrown by SurfaceMountingManager.addViewAt:390 as IllegalStateException: addViewAt: failed to insert view [N] into parent [M] at index 1.

APP-H7A — remove path

com.facebook.react.fabric.FabricUIManager$DispatchUIFrameCallback.doFrameGuarded(FabricUIManager.java:1568)
com.facebook.react.fabric.mounting.MountItemDispatcher.dispatchMountItems(MountItemDispatcher.kt:246)
com.facebook.react.fabric.mounting.mountitems.IntBufferBatchMountItem.execute(IntBufferBatchMountItem.kt:125)
com.facebook.react.fabric.mounting.SurfaceMountingManager.removeViewAt(SurfaceMountingManager.kt:415)

Throw: IllegalStateException: Unable to remove a view from a view that is not a ViewGroup. ParentTag: N - Tag: M - Index: K.

Suspected cause

Fabric applies a batch of mount items against a native view hierarchy that has already diverged from the shadow tree the batch was computed against. The insert case lands in ReactClippingViewManager, so the removeClippedSubviews path is the strongest lead — clipped children are added and removed outside the normal mount sequence, which lets the parent's real child count fall out of step with the index Fabric asks for. The remove case fails the same way from the other direction: the recorded parent tag no longer resolves to a ViewGroup.

Worth checking whether either regressed with the RN 0.85/0.86 upgrade. APP-H7A first appeared 2026-07-07, which is close to that work.

Reproduction

Unknown. Both are fatal and low-frequency per user (roughly one event per affected user), which is consistent with a timing-dependent mount race rather than a deterministic screen. See the Sentry events for device and navigation context.

Starting points:

  1. Exercise fast navigation in and out of TabNavigator / Inbox on Android while list content is still streaming in.
  2. Look for components in that path that set removeClippedSubviews and also mutate children asynchronously.

Related

Upwork Automation - Do Not Edit
Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. self-assigned this
    on Aug 17, 2026
  2. added
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Aug 17, 2026
  3. melvin-bot commented on Aug 17, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @linhvovan29546 (External)

  4. melvin-bot commented on Aug 17, 2026

    @melvin-bot
  5. MelvinBot commented on Aug 17, 2026

    @MelvinBot
    Contributor

    Proposal

    What is the root cause of that problem?

    The Inbox/LHN report list passes removeClippedSubviews to a FlashList v2 (@shopify/flash-list 2.3.0) at LHNOptionsList.tsx:179. This is the only virtualized list in the TabNavigator → Inbox chain, which matches the affected views on both Sentry crashes exactly.

    FlashList v2 is a pure-JS recycler and does not consume removeClippedSubviews — the prop falls through its ...rest and is spread onto the underlying RN ScrollView. On Android that activates ReactClippingViewManager, which adds and removes clipped children outside the normal Fabric mount sequence. When Fabric later applies a batch of mount items (IntBufferBatchMountItem → SurfaceMountingManager.addViewAt/removeViewAt), the parent's real child count/tree has already diverged from the shadow tree the batch was computed against, so:

    • APP-7AR (insert): IndexOutOfBoundsException: index=1 count=0 → rethrown as addViewAt: failed to insert view into parent — lands in ReactClippingViewManager.addView, confirming the clipping path.
    • APP-H7A (remove): the recorded parent tag no longer resolves to a ViewGroup → Unable to remove a view from a view that is not a ViewGroup.

    Because FlashList v2 already does its own view recycling, removeClippedSubviews here is redundant and harmful — it double-manages the same children that Fabric is also mounting/unmounting, which is the timing-dependent race described in the issue. The same anti-pattern is repeated on the Search-tab FlashLists (BaseSearchList/index.native.tsx:46, SearchStaticList.tsx:382).

    What changes do you think we should make in order to solve the problem?

    Remove removeClippedSubviews from the FlashList v2 instances (or gate it to false on Android). Primary fix at LHNOptionsList.tsx:179; apply the same treatment to the Search FlashLists so the crash can't resurface there. FlashList v2 recycles views itself, so dropping the prop is functionally a no-op for scrolling perf while eliminating the RN clipping path the crash originates from. The codebase already treats this prop as risky and disables it explicitly elsewhere (e.g. removeClippedSubviews={false} in BaseAutoCompleteSuggestions.tsx).

    What alternative solutions did you explore? (Optional)

    A native-side guard in ReactClippingViewManager/SurfaceMountingManager would be more general but is stock RN 0.86.0 code — App does not patch ReactClippingViewManager, and there is already an iOS-only recycle-safety patch (react-native+0.86.0+032, which resets _removeClippedSubviews = NO on recycle) with no Android equivalent. A patch there is higher-risk and broader than needed given the JS-side prop is the direct trigger.

    Investigation details & evidence

    Chain to the list: TabNavigator.native.tsx → REPORTS_SPLIT_NAVIGATOR → ReportsSplitNavigator (sidebar = SCREENS.INBOX) → SidebarLinks.tsx:110 <LHNOptionsList> → FlashList at LHNOptionsList.tsx:179. The bottom tab bar itself contains no virtualized list, so the "default-true on Android" concern doesn't apply there — this list sets the prop explicitly.

    Prop leak: In @shopify/flash-list@2.3.0, dist/recyclerview/RecyclerView.js destructures props without extracting removeClippedSubviews (it lands in ...rest) and spreads ...rest onto the internal RN ScrollView — so the prop reaches the native Android ReactClippingViewManager path from the crash stack.

    Crash signature nuance: Both are fatal native IllegalStateException/IndexOutOfBounds throws from ViewGroup.addView/removeView, i.e. a genuine tree/index divergence — distinct from the soft-logged missing-viewState handling that RN 0.86.0 upstreamed for addViewAt/removeViewAt (see App patch +038 details.md). So this is a real mount-ordering race, not a missing-viewState blank screen.

    RN-upgrade timeline (the issue's regression suspicion): RN went 0.83.1 → 0.85.3 (PR #92484, merged 2026-07-09) → 0.86.0 (PR #96372, merged 2026-08-10). APP-H7A first-seen 2026-07-07 is ~2 days before 0.85.3 merged to main, but PR #92484 was open from 2026-06-03, so early events likely came from 0.85.3 ad-hoc/test builds. Whether the FlashList-v2 + removeClippedSubviews combination (or the RN bump) is what tipped it should be confirmed by bucketing APP-7AR/APP-H7A events by app version in Sentry. Note the current App HEAD (ca6b99d) is a revert of PR #96772 — worth checking whether that PR touched LHN/FlashList clipping.

    Low-risk validation: ship removeClippedSubviews={false} on Android at LHNOptionsList.tsx:179 (or behind a small experiment) and watch APP-7AR/APP-H7A stop.

    Related issues


    Next Steps for Contributor+ team:
    To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/98791) to create a draft PR.
    To refine: @MelvinBot <your feedback>
    To reject: Explain why you are rejecting Melvin's proposal.

  6. linhvovan29546 commented on Aug 18, 2026

    @linhvovan29546
    Contributor

    🆘 C+ Help Wanted

  7. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Aug 18, 2026
  8. abbasifaizan70 commented on Aug 18, 2026

    @abbasifaizan70
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    On Android HybridApp, the Fabric renderer is fatally crashing while mounting/unmounting rows in the Inbox (LHN) list, inside the TabNavigator stack. Two related native crashes are reported in Sentry:

    • APP-7AR: IllegalStateException: addViewAt: failed to insert view into parent — thrown from ReactClippingViewManager.addView when the underlying IndexOutOfBoundsException: index=1 count=0 occurs (Fabric asks to insert a child at index 1 into a native ViewGroup that currently has 0 real children attached).
    • APP-H7A: IllegalStateException: Unable to remove a view from a view that is not a ViewGroup — thrown from SurfaceMountingManager.removeViewAt when the parent tag Fabric recorded no longer resolves to an actual ViewGroup.

    Both are timing-dependent (roughly one crash per affected user) and both bottom out in ReactClippingViewManager, which is the native view manager that only gets exercised when a scrollable container is rendered with removeClippedSubviews.

    What is the root cause of that problem?

    The Inbox list (LHNOptionsList) renders its FlashList with removeClippedSubviews enabled:

    <FlashList
    ref={flashListRef}
    indicatorStyle="white"
    keyboardShouldPersistTaps="always"
    CellRendererComponent={OptionRowRendererComponent}
    contentContainerStyle={StyleSheet.flatten(contentContainerStyles)}
    data={data}
    testID="lhn-options-list"
    keyExtractor={keyExtractor}
    renderItem={renderItem}
    extraData={extraData}
    showsVerticalScrollIndicator={false}
    onLayout={onLayout}
    onScroll={onScroll}
    initialScrollIndex={initialScrollIndex}
    maintainVisibleContentPosition={{disabled: true}}
    drawDistance={250}
    removeClippedSubviews
    />

    removeClippedSubviews is a legacy View/ScrollView optimization: on Android it turns the scroll content's container into a ReactClippingViewGroup, whose native code independently tracks all logical children versus the subset that is currently attached to the real ViewGroup (children outside the clipping rect are physically detached). Crucially, this attach/detach bookkeeping is driven by scroll-position recalculations on the UI thread and is not part of Fabric's serialized mount-item queue — it mutates the same native child array that Fabric's SurfaceMountingManager.addViewAt/removeViewAt also mutate when applying the next batch of mount instructions.

    @shopify/flash-list (package.json pins 2.3.0) does its own item virtualization/recycling (a bounded pool of cell views repositioned as the user scrolls, further limited here by drawDistance={250}), so this prop is simply spread through to FlashList's internal CompatScrollView — it isn't something FlashList implements or needs; it just re-enables the same RN-core clipping code path that any classic ScrollView/FlatList would get. Layering that independent, UI-thread-driven clipping mutation on top of FlashList's own recycling gives two systems (Fabric mounting + native clipping) uncoordinated write access to the same view hierarchy. When fast navigation in/out of the Inbox/TabNavigator route interleaves a Fabric mount batch (adding/removing LHN rows as reports/reportAttributes stream in from Onyx) with a clipping recalculation triggered by the same scroll/layout pass, the two can disagree about the container's actual child count or about whether a given tag is still a live ViewGroup:

    • If clipping has detached children the shadow tree still expects to be present, a subsequent addViewAt is issued for an index beyond what's really attached → IndexOutOfBoundsException/addViewAt failure (APP-7AR).
    • If clipping (or a recycle/detach from FlashList itself) has already torn down a parent, a queued removeViewAt for that stale tag fails because the tag no longer resolves to a ViewGroup (APP-H7A).

    This matches the issue's own "suspected cause" and the stack traces exactly (ReactClippingViewManager.addView in the insert path). It's also consistent with community reports against flash-list where disabling removeClippedSubviews resolves otherwise-unexplained view-state/rendering bugs — the prop is a known-unsafe combination with FlashList's recycling model, and this codebase already avoids it elsewhere for exactly that class of risk (the mention list's FlatList explicitly hardcodes it off):

    <FlatList
    ref={scrollRef}
    keyboardShouldPersistTaps="handled"
    data={suggestions}
    renderItem={renderItem}
    keyExtractor={keyExtractor}
    removeClippedSubviews={false}
    showsVerticalScrollIndicator={innerHeight > rowHeight.get()}
    extraData={[highlightedSuggestionIndex, renderSuggestionMenuItem]}
    style={styles.overscrollBehaviorContain}
    />

    What changes do you think we should make in order to solve the problem?

    Remove removeClippedSubviews from the Inbox list's FlashList, the same way BaseAutoCompleteSuggestionsImpl already opts out of it on its list:

                        drawDistance={250}

    (i.e. delete the removeClippedSubviews line entirely — FlashList already virtualizes rows via its own recycler and drawDistance, so no replacement prop is needed.)

    This is the minimal, best-practice fix because:

    • It removes the redundant/unsafe optimization rather than papering over the native race (no try/catch, no retry, no feature-flag gating around a known-buggy native path).
    • It reuses the exact pattern already established in this codebase for another removeClippedSubviews list, so it's consistent with existing conventions rather than introducing a new one.
    • FlashList still bounds the number of rendered/recycled rows via its own virtualization plus the existing drawDistance={250}, so scroll performance for the LHN — which was the only reason removeClippedSubviews would have been added — is unaffected.

    Edge cases:

    • Android (the crashing platform): this removes the ReactClippingViewGroup/ReactClippingViewManager code path entirely for this list, eliminating the race between Fabric's mount-item queue and native clip-driven attach/detach — directly addressing both APP-7AR and APP-H7A.
    • iOS: removeClippedSubviews is implemented differently there and isn't implicated by either stack trace; removing it is still safe since FlashList's own recycling already provides the virtualization benefit.
    • Web: the prop is a native-only concept and is a no-op through react-native-web, so there is no behavior change to verify there.
    • Offline / streaming data: unrelated to this change — it doesn't touch how reports/reportAttributes are fetched or rendered, only how the scroll container manages its native children, so optimistic updates and offline queueing are unaffected.
    • Existing callers: removeClippedSubviews is set directly on the FlashList inside LHNOptionsList, not exposed via LHNOptionsListProps, so no caller of LHNOptionsList is affected by this change.
    • Fast repeated navigation in/out of Inbox/TabNavigator (the reported repro pattern) should be specifically retested on a physical/emulated Android device with new-architecture enabled, since that's the timing-dependent condition that surfaced the crash.
  9. mukhrr commented on Aug 18, 2026

    @mukhrr
    Contributor

    🚨 Edited by proposal-police: This proposal was edited at 2026-08-18 13:56:07 UTC.

    Proposal

    What is the root cause of that problem?

    I opened the actual @shopify/flash-list@2.3.0 package this app ships and traced where removeClippedSubviews goes once it leaves LHNOptionsList.

    <FlashList
    ref={flashListRef}
    indicatorStyle="white"
    keyboardShouldPersistTaps="always"
    CellRendererComponent={OptionRowRendererComponent}
    contentContainerStyle={StyleSheet.flatten(contentContainerStyles)}
    data={data}
    testID="lhn-options-list"
    keyExtractor={keyExtractor}
    renderItem={renderItem}
    extraData={extraData}
    showsVerticalScrollIndicator={false}
    onLayout={onLayout}
    onScroll={onScroll}
    initialScrollIndex={initialScrollIndex}
    maintainVisibleContentPosition={{disabled: true}}
    drawDistance={250}
    removeClippedSubviews
    />

    • LHNOptionsList passes a bare removeClippedSubviews (so true) straight into <FlashList>.
    • RecyclerView.js in @shopify/flash-list@2.3.0 destructures a long list of known props but never touches removeClippedSubviews, so it falls into the leftover ...rest object.
    • That same file spreads ...rest onto CompatScrollView, which resolves to Animated.ScrollView, React Native's own ScrollView, not anything FlashList manages itself.
    • React Native's ScrollView.js forwards removeClippedSubviews straight onto NativeScrollContentView, and on Android that is exactly ReactClippingViewManager, the class named in the APP-7AR stack trace.
    • I rendered LHNOptionsList in a Jest harness with the platform mocked to android and queried the actual host node by testID="lhn-options-list": on current code its removeClippedSubviews prop resolves to true on the real RCTScrollView host, not just on the <FlashList> JSX, so the leak is observable in the rendered tree, not only in the library source.
    • FlashList already recycles and windows its own children through its ViewHolderCollection and drawDistance={250}, so turning on native clipping on top of that makes two systems add and remove the same child views on different schedules, one through Fabric's mount batches and one through the classic RN clipping pass outside them. That is what lets a parent's real child count fall out of step with the index a mount batch was computed against, matching both the insert (index=1 count=0) and remove (parent tag no longer a ViewGroup) failures.

    I also checked the RN-upgrade theory the issue itself raises. The flash-list v1 to v2 migration landed 2025-09-09, about six months before APP-7AR's first-seen date of 2026-03-11, so the leak has been present since that migration and isn't new. Whatever shifted the timing odds around March wasn't the FlashList version bump, and I didn't chase that further since it isn't needed to fix the crash.

    What changes do you think we should make in order to solve the problem?

    I disabled removeClippedSubviews on Android only, since platform is already computed at module scope in this file:

                        drawDistance={250}
    -                    removeClippedSubviews
    +                    removeClippedSubviews={platform !== CONST.PLATFORM.ANDROID}

    App/src/CONST/index.ts

    Lines 1059 to 1064 in c7b8272

    PLATFORM: {
    IOS: 'ios',
    ANDROID: 'android',
    WEB: 'web',
    MOBILE_WEB: 'mobileweb',
    },

    With this change the same Jest harness shows the host RCTScrollView node's removeClippedSubviews resolving to false on Android. I added a regression test, tests/ui/components/LHNOptionsListRemoveClippedSubviewsTest.tsx, that reads that prop off the real scroll host rather than off the <FlashList> element; it fails against current main (receives true) and passes with this change.

    What alternative solutions did you explore? (Optional)

    I considered dropping removeClippedSubviews on every platform and widening the fix to the Search tab's FlashLists, since they set the same prop. I kept the change Android-only and scoped to LHNOptionsList instead: with platform !== CONST.PLATFORM.ANDROID, the value on iOS and web stays true, identical to what ships today, so there's no regression surface off Android. Sentry's own "Affected view(s)" for both issues names only TabNavigator and Inbox, so I didn't touch the Search lists without a crash report pointing at them.

    I also considered catching the addViewAt/removeViewAt exceptions in SurfaceMountingManager instead, but that would leave the native and shadow trees diverged and could drop the rest of the mount transaction or render stale content. Removing the clipping path that causes the divergence is the smaller, root-cause fix.

    The codebase already avoids this same prop on a different asynchronously changing list:

    <FlatList
    ref={scrollRef}
    keyboardShouldPersistTaps="handled"
    data={suggestions}
    renderItem={renderItem}
    keyExtractor={keyExtractor}
    removeClippedSubviews={false}
    showsVerticalScrollIndicator={innerHeight > rowHeight.get()}
    extraData={[highlightedSuggestionIndex, renderSuggestionMenuItem]}
    style={styles.overscrollBehaviorContain}

    And RN 0.86.0's own patch notes confirm the nullable-state guards for addViewAt/removeViewAt only cover a missing view state, not a parent whose child tree has diverged, which is why they can't mask this crash:

    ### [react-native+0.86.0+038+log-soft-exception-if-viewState-not-found.patch](react-native+0.86.0+038+log-soft-exception-if-viewState-not-found.patch)
    - Reason: Restores the Android `updateOverflowInset` half of the dropped `react-native+0.85.3+025+log-soft-exception-if-viewState-not-found.patch`. `SurfaceMountingManager.updateOverflowInset` still resolves its tag through the throwing `getViewState`, so an `INSTRUCTION_UPDATE_OVERFLOW_INSET` op for a view that was already unmounted throws `RetryableMountingLayerException` from inside `IntBufferBatchMountItem.execute`. `MountItemDispatcher.dispatchMountItems` only retries `DispatchCommandMountItem`s, and `RetryableMountingLayerException` is not a `ReactIgnorableMountingException`, so the exception is rethrown and every remaining instruction in that mount transaction is dropped — the incoming views are created but never added or laid out, leaving a blank screen. This patch resolves the tag with `getNullableViewState` and soft-logs + returns instead, matching what upstream already does for `addViewAt`, `updateProps` and `updateLayout`.
    - Upstream PR/issue: [#49077](https://github.com/facebook/react-native/issues/49077) [#56762](https://github.com/facebook/react-native/pull/56762) [#7493](https://github.com/software-mansion/react-native-reanimated/issues/7493)
    - E/App issues: [#82611](https://github.com/Expensify/App/issues/82611) [#93833](https://github.com/Expensify/App/issues/93833)
    - PR introducing patch: [#84303](https://github.com/Expensify/App/pull/84303) (original 0.85.3 patch)
    - 0.86.0 migration note: RN 0.86.0 upstreamed the `getNullableViewState` + soft-log guard for `addViewAt`, `updateProps`, `updateLayout` and `removeViewAt`, which is why the 0.85.3 patch was dropped during the upgrade — but it did **not** upstream the `updateOverflowInset` guard, so that one site regressed. Only that site is re-patched here; `updatePadding` and `updateState` still use the throwing `getViewState`, matching 0.85.3 behaviour. Re-check on the RN 0.87 upgrade whether `updateOverflowInset` has been guarded upstream, and drop this patch if so.

  10. Abdulloh0109 commented on Aug 18, 2026

    @Abdulloh0109
    Contributor

    🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.

  11. 136 remaining items

  12. mallenexpensify commented on Oct 5, 2026

    @mallenexpensify
    Contributor

    @MelvinBot @samranahm was hired for this job in Upwork, how and why?

  13. oqildev commented on Oct 5, 2026

    @oqildev
    Contributor

    Payment Summary

    Contributor: @oqildev due $250 via Upwork Contributor+: @linhvovan29546 due $250 via NewDot

    @oqildev can you please accept the job below? Please reply here and tag me once you have. https://www.upwork.com/jobs/~022107095812109235453

    @linhvovan29546 plz complete the Contributor+ checklist and tag me in a post once you have. Thx

    @mallenexpensify
    Yes. I accepted the job.

  14. MelvinBot commented on Oct 5, 2026

    @MelvinBot
    Contributor

    samranahm was never selected for this job. The Upwork hire came from the profile link SARAMALI15792 gave you. The Upwork account behind that link appears to be the one you see as samranahm.

    Timeline
    • Aug 18: samranahm posted a proposal. ProposalPolice withdrew it as a duplicate. No one selected it.
    • Aug 24: SARAMALI15792 was assigned. They said the Upwork job returned a 403 and shared this profile: https://www.upwork.com/freelancers/~012263396cc08bc99c (comment).
    • Aug 25: You asked for their Upwork profile link and hired them (comment). They then reported a $14 offer. You sent a new $250 offer, and they accepted it.
    • On another issue, SARAMALI15792 registered the same Upwork profile ID with the email saramali15792@gmail.com (comment).

    I can't see Upwork, so I can't confirm who owns that profile. If it shows as samranahm, check whether the two GitHub accounts share one Upwork account.

    Their PR, Fix Fabric mounting-transaction merge order picking oldest instead of newest pending transaction (APP-7AR), was closed. The C+ later chose oqildev's proposal. You can likely end that contract without payment.


    view run

  15. samranahm commented on Oct 5, 2026

    @samranahm
    Contributor

    @mallenexpensify It's not me, it was @SARAMALI15792 #98791 (comment), we previously decided to go with @SARAMALI15792's proposal but later changed to @oqildev

  16. linhvovan29546 commented on Oct 5, 2026

    @linhvovan29546
    Contributor

    @mallenexpensify Sorry, I forgot about this. It’s complete now.

  17. mallenexpensify commented on Oct 5, 2026

    @mallenexpensify
    Contributor

    @oqildev paid, leaving open for further review

  18. mountiny commented on Oct 7, 2026

    @mountiny
    ContributorAuthor

    (Vit's agent) Agreed, APP-H7A is a separate issue. It now has its own tracker: [Sentry: APP-H7A] Fabric removeViewAt crashes removing view from non-ViewGroup parent.

    • The APP-7AR fix did not touch it. On builds with #101057 (9.4.93-3 and later), APP-7AR has 2 events. APP-H7A has 7 events from 6 users on those same builds. Its overall rate barely moved: 24 events in the 14 days before the deploy, 18 in the 13 days after.
    • The failure is different. APP-7AR is a stale index into a real ViewGroup. APP-H7A throws when the parent tag has a ViewState whose view is null or not a ViewGroup (SurfaceMountingManager.kt at v0.86.0).
    • It is the remove-side twin of APP-K0G. [$175] [Sentry: APP-K0G] Fabric addViewAt crashes adding view into non-ViewGroup throws on the same check in addViewAt.
    • Upstream already fixed this exact throw. react-native@3f553d7 turns it into a soft exception. It landed after 0.86.0, so our build still crashes. #102901 cites that commit but only patches addViewAt.

    Next steps:

    1. Track APP-H7A in #103369, as a sibling of #102741.
    2. Fix it with a backport of react-native@3f553d7 as a new RN patch.
    3. Close this issue once payment is done, since APP-7AR is fixed.
  19. twisterdotcom commented on Oct 12, 2026

    @twisterdotcom
    Contributor
  20. linhvovan29546 commented on Oct 13, 2026

    @linhvovan29546
    Contributor

    I think this is good to close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions