react / react/react-native

Bug Report: Duplicate RCTSwiftUI Symbol Leakage Causes lowercaseString Crash in RN 0.84 Prebuilt Frameworks

未关闭
#55,978 5 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

Needs: Attention Needs: Version Info
主要语言
C++
星标
127k
派生
25.3k
平均合并
1 天 23 小时
30 天内合并 PR
4

描述

Description

Description
In React Native 0.84 (New Architecture), apps that include custom Swift modules or import React in AppDelegate.swift crash deterministically on iOS launch before the JS bundle evaluates. The crash is -[NSMallocBlock lowercaseString]: unrecognized selector sent to instance.

Root Cause Analysis:
This is a framework-level linker bug caused by the new prebuilt React.framework and ENABLE_DEBUG_DYLIB features.

React.framework (and the .debug.dylib) comes prebuilt with exposed Swift symbols, specifically RCTSwiftUI and RCTEventEmitter.

When the main app target compiles AppDelegate.swift (which imports React), the Swift compiler statically links those exposed RCTSwiftUI symbols directly into the main app executable.

At runtime, dyld loads the main executable AND the React.framework (or .debug.dylib). Both binaries now contain the exact same Swift classes.

The Objective-C runtime duplicate class registration corrupts the dispatch table. When the TurboModule system initializes, it sends a string method (lowercaseString) to a corrupted pointer (an NSMallocBlock), causing a fatal crash.

Steps to reproduce

Steps to Reproduce:

Initialize a React Native 0.84 project with New Architecture enabled.

Add a basic Swift file to the main iOS target that imports React (or just rely on the default AppDelegate.swift).

Build for an iOS physical device (xcodebuild -workspace ...).

Crash occurs immediately upon boot.
(Note: Setting ENABLE_DEBUG_DYLIB=NO strips the dylib, but the crash persists because the duplicate symbols still exist between the main executable and the prebuilt React.framework).

Expected Behavior
Prebuilt React frameworks should have their internal Swift symbols (like RCTSwiftUI) stripped or marked with hidden visibility so they do not leak into the consumer's main app binary during compilation.

React Native Version

0.84.x

Affected Platforms

Runtime - iOS

Output of npx @react-native-community/cli info
System:
  OS: macOS 15.7.4
  CPU: (10) arm64 Apple M4
  Memory: 2.81 GB / 24.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 24.12.0
    path: /Users/avacado/.nvm/versions/node/v24.12.0/bin/node
  Yarn: Not Found
  npm:
    version: 11.6.2
    path: /Users/avacado/.nvm/versions/node/v24.12.0/bin/npm
  Watchman:
    version: 2026.01.12.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.16.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 25.2
      - iOS 26.2
      - macOS 26.2
      - tvOS 26.2
      - visionOS 26.2
      - watchOS 26.2
  Android SDK: Not Found
IDEs:
  Android Studio: 2025.3 AI-253.29346.138.2531.14876573
  Xcode:
    version: 26.3/17C529
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.18
    path: /opt/homebrew/opt/openjdk@17/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/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.84.1
    wanted: ^0.84.1
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: true
  newArchEnabled: true
Stacktrace or Logs
Fatal Exception: NSInvalidArgumentException
-[__NSMallocBlock__ lowercaseString]: unrecognized selector sent to instance

Crash Timeline Context:
1. iOS launches the app binary successfully.
2. React Native's prebuilt React.framework loads (registers RCTSwiftUI / RCTEventEmitter classes).
3. LocalMind.debug.dylib loads (registers duplicate RCTSwiftUI / RCTEventEmitter classes).
4. Duplicate class registration corrupts the Objective-C runtime dispatch table.
5. React Native attempts to evaluate the JavaScript bundle.
6. A TurboModule or Event Emitter attempts string manipulation, routing the method to a corrupted pointer (a memory block instead of an NSString).
7. Hard crash before any application-level JS or native code can execute.

Note: Setting ENABLE_DEBUG_DYLIB=NO in the xcodebuild command successfully strips the .debug.dylib, but the crash persists because the main application executable still statically links the duplicate RCTSwiftUI symbols from AppDelegate.swift importing the prebuilt React.framework.
MANDATORY Reproducer

https://github.com/marinoonthelake-blip/test

Screenshots and Videos

N/A - This is a deterministic compiler/linker crash that occurs at launch before the React Native view hierarchy is mounted.

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

从导入 React 的必需 reproducer 和默认 AppDelegate.swift 路径开始,然后检查预构建的 React.framework 和 .debug.dylib 是如何生成并由 xcodebuild 链接的。验证 app 和 framework 输出中的重复 RCTSwiftUI 和 RCTEventEmitter 符号;当 reproducer 能够在不发生 lowercaseString 崩溃的情况下启动,并且 consumer 二进制文件不再包含重复符号时,即表示完成。

由索引模型根据 Issue 内容生成。

评估

技术栈
ios, react-native, swift
领域
build-system, mobile
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
基本清楚
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。