[Android] Missing native component crashes Fabric instead of rendering UnimplementedNativeView
还没有人认领这个 Issue。
- 主要语言
- C++
- 星标
- 127k
- 派生
- 25.3k
- 平均合并
- 1 天 23 小时
- 30 天内合并 PR
- 4
描述
Description
On Android, mounting a Fabric component whose native ViewManager is missing from the binary throws IllegalViewOperationException and tears down the surface. On iOS the same app renders the UnimplementedNativeView placeholder and keeps running. Reproduced on RN 0.86.0 with the New Architecture on both platforms.
The cause is in ComponentDescriptorRegistry::at(): an unknown component name is assumed to be a legacy view and gets an UnstableLegacyViewManagerAutomaticComponentDescriptor. Since useFabricInterop() defaults to true, the UnimplementedNativeViewComponentDescriptor branch never runs. Nothing checks the assumption, so the failure lands at mount in SurfaceMountingManager → ViewManagerRegistry.get(), which throws. Android does install the fallback, and the crash message itself lists UnimplementedNativeView among the registered ViewManagers. It's wired up and simply unreachable. iOS doesn't have this problem because RCTComponentViewFactory checks isSupported: before taking the interop path and otherwise falls through to the placeholder.
JS can't catch it earlier: under bridgeless, view configs come from static Codegen definitions and the native side is never consulted.
Any app with a library's JS installed but its native code absent hits this: a dependency added without rebuilding, or a build that predates it.
Expected: Android behaves like iOS, rendering the placeholder plus a log naming the missing component. The name matters, since today's crash at least identifies the component and a silent placeholder would hide the problem entirely.
Steps to reproduce
- Clone https://github.com/TaduJR/rn-repro-fabric-interop-viewmanager the entire reproducer is
App.tsx, which registers a Fabric component (viaNativeComponentRegistry.get, the same registration Codegen emits) under a name no native code provides. Node 24+ required (the config files are TypeScript). npm installnpx react-native run-android- The screen shows
Fabric = true, bridgeless = trueandhasViewManagerConfig(ThisNativeComponentIsNotInTheBinary) = false, confirming the component exists in no native registry. - Press Mount the component.
- The surface crashes with
IllegalViewOperationExceptioninstead of rendering theUnimplementedNativeViewplaceholder.
React Native Version
0.86.0
Affected Platforms
Runtime - Android, Build - MacOS
Areas
Fabric - The New Renderer, Codegen
Output of npx @react-native-community/cli info
System:
OS: macOS 26.5.2
CPU: (14) arm64 Apple M4 Pro
Memory: 194.66 MB / 24.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 24.13.0
path: /Users/natu/.nvm/versions/node/v24.13.0/bin/node
Yarn:
version: 1.22.22
path: /Users/natu/.nvm/versions/node/v24.13.0/bin/yarn
npm:
version: 11.6.2
path: /Users/natu/.nvm/versions/node/v24.13.0/bin/npm
Watchman:
version: 2026.03.16.00
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.16.2
path: /Users/natu/.rbenv/shims/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 25.5
- iOS 26.5
- macOS 26.5
- tvOS 26.5
- visionOS 26.5
- watchOS 26.5
Android SDK:
API Levels:
- "33"
- "34"
- "36"
- "36"
- "37"
Build Tools:
- 35.0.0
- 36.0.0
- 36.1.0
- 37.0.0
System Images:
- android-35 | Google Play Tablet ARM 64 v8a
- android-36.1 | Google Play ARM 64 v8a
- android-36 | Google Play ARM 64 v8a
- android-36 | Pre-Release 16 KB Page Size Google Play ARM 64 v8a
- android-37.0 | 16 KB Page Size Google Play ARM 64 v8a
- android-37.0 | 16 KB Page Size Google APIs ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: 2026.1 AI-261.23567.138.2611.15646644
Xcode:
version: 26.6/17F113
path: /usr/bin/xcodebuild
Languages:
Java:
version: 25.0.3
path: /usr/bin/javac
Ruby:
version: 3.3.4
path: /Users/natu/.rbenv/shims/ruby
npmPackages:
"@react-native-community/cli":
installed: 20.1.0
wanted: 20.1.0
react:
installed: 19.2.3
wanted: 19.2.3
react-native:
installed: 0.86.0
wanted: 0.86.0
react-native-macos: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: true
iOS:
hermesEnabled: true
newArchEnabled: true
Stacktrace or Logs
com.facebook.react.uimanager.IllegalViewOperationException: Can't find ViewManager 'ThisNativeComponentIsNotInTheBinary' nor 'RCTThisNativeComponentIsNotInTheBinary' in ViewManagerRegistry, existing names are: [DebuggingOverlay, RCTSafeAreaView, RCTModalHostView, AndroidProgressBar, AndroidHorizontalScrollView, RCTImageView, RCTText, AndroidHorizontalScrollContentView, UnimplementedNativeView, RCTScrollView, RCTView, AndroidDrawerLayout, AndroidSwitch, AndroidSwipeRefreshLayout, AndroidTextInput, RCTSelectableText, VirtualView]
at com.facebook.react.uimanager.ViewManagerRegistry.get(ViewManagerRegistry.kt:72)
at com.facebook.react.fabric.mounting.SurfaceMountingManager.createViewUnsafe(SurfaceMountingManager.kt:610)
at com.facebook.react.fabric.mounting.SurfaceMountingManager.preallocateView(SurfaceMountingManager.kt:1104)
at com.facebook.react.fabric.mounting.mountitems.PreAllocateViewMountItem.execute(PreAllocateViewMountItem.kt:39)
at com.facebook.react.fabric.mounting.MountItemDispatcher.executeOrEnqueue(MountItemDispatcher.kt:379)
at com.facebook.react.fabric.mounting.MountItemDispatcher.dispatchPreMountItemsImpl(MountItemDispatcher.kt:331)
at com.facebook.react.fabric.mounting.MountItemDispatcher.dispatchPreMountItems(MountItemDispatcher.kt:325)
at com.facebook.react.fabric.FabricUIManager$DispatchUIFrameCallback.doFrameGuarded(FabricUIManager.java:1623)
at com.facebook.react.uimanager.GuardedFrameCallback.doFrame(GuardedFrameCallback.kt:42)
at com.facebook.react.modules.core.ReactChoreographer.frameCallback$lambda$1(ReactChoreographer.kt:58)
at android.view.Choreographer.doCallbacks(Choreographer.java:1252)
at android.view.Choreographer.doFrame(Choreographer.java:1205)
at android.os.Looper.loop(Looper.java:397)
at android.app.ActivityThread.main(ActivityThread.java:9523)
MANDATORY Reproducer
https://github.com/TaduJR/rn-repro-fabric-interop-viewmanager
Screenshots and Videos
Android:
iOS:
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从 ComponentDescriptorRegistry::at() 开始,沿着 Android 通过 SurfaceMountingManager 和 ViewManagerRegistry.get() 的挂载路径进行追踪。将 Android 的行为与 iOS 上 RCTComponentViewFactory 的支持检查和回退路径进行比较。使用强制复现用例验证:缺失的原生组件会渲染 UnimplementedNativeView,使 surface 保持运行,并记录缺失组件的名称。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- android, cpp, kotlin, typescript
- 领域
- frontend, mobile
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 冷清
- 描述清晰度
- 描述清楚
- 新手友好度
- 55/100