react / react/react-native

Setting caretHidden for a TextInput component on iOS (iPhone SE 3) causes continuous metal rendering errors

Offen
#58,157 1 Kommentar 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Component: TextInput Needs: Triage :mag: Platform: iOS
Vorherrschende Sprache
C++
Sterne
127k
Forks
25.3k
Ø Merge
1 T. 23 Std.
Gemergte PRs (30 T.)
4

Beschreibung

Description

Setting the caretHidden prop on a <TextInput> component when rendered on iOS results in an error that spams the iOS logs (~ 20-30 times per second):

Surface 1073741823 x 1073741823 is too large

As the error is generated so frequently this creates a lot of activity on the app. In my use case this is causing XCUITest to wait continuously for the app to be idle which never happens, so our end to end tests tend to stall when displaying a text input with a hidden caret.

We are using the iPhone SE 3 in the simulator for our testing which shows the error, it does not seem to occur with the iPhone 17 Pro, I haven't tested other phones but the obvious difference is the home button on the SE 3. I was able to reproduce this problem on a fresh v0.87 metro app with a single text input.

I believe this may be due to calculations that use the caret position that run even though the caret is not displayed, though I'm not 100% sure.

RCTUITextField.mm (for single line input) and RCTUITextView.mm for multi line input both set the caret to CGRectZero which would give it dimensions and size of 0, which I could see causing the problem, though I'm not sure what code is using these values for calculations.

Steps to reproduce
  1. Install the app with npm install
  2. Run the app on iOS on the iPhone SE 3 with npm run ios -- --simulator="iPhone SE 3"
  3. Open the Console.app and start viewing logs for the simulator (you can filter by metal to make the error more clear)
  4. Focus the input field by tapping on it
  5. Check the errors in the console app
React Native Version

0.87.1

Affected Platforms

Runtime - iOS

Output of npx @react-native-community/cli info
System:
  OS: macOS 26.6.2
  CPU: (14) arm64 Apple M4 Pro
  Memory: 435.84 MB / 48.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 24.11.0
    path: /Users/mario/.local/share/mise/installs/node/24.11.0/bin/node
  Yarn:
    version: 1.22.22
    path: /Users/mario/.local/share/mise/installs/node/24.11.0/bin/yarn
  npm:
    version: 11.6.1
    path: /Users/mario/.local/share/mise/installs/node/24.11.0/bin/npm
  Watchman:
    version: 2026.01.12.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.16.2
    path: /Users/mario/.local/share/mise/installs/ruby/3.4.8/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:
    API Levels:
      - "29"
      - "33"
      - "35"
      - "36"
    Build Tools:
      - 33.0.2
      - 35.0.0
      - 36.0.0
    System Images:
      - android-28 | Google APIs ARM 64 v8a
      - android-29 | Google APIs ARM 64 v8a
    Android NDK: Not Found
IDEs:
  Android Studio: 2025.3 AI-253.32098.37.2534.15336583
  Xcode:
    version: 26.2/17C52
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: javac 17
    path: /Users/mario/.local/share/mise/shims/javac
  Ruby:
    version: 3.4.8
    path: /Users/mario/.local/share/mise/installs/ruby/3.4.8/bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 20.2.0
    wanted: 20.2.0
  react:
    installed: 19.2.3
    wanted: 19.2.3
  react-native:
    installed: 0.87.1
    wanted: 0.87.1
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: true
  newArchEnabled: true
Stacktrace or Logs
Subsystem: com.apple.coreanimation
Category: Metal
Surface 1073741823 x 1073741823 is too large
MANDATORY Reproducer

https://github.com/mariovisic/react-native-example-ios-carret-error

Screenshots and Videos
Image

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Rechercherichtung

Reproduziere das Problem mit der obligatorischen Beispiel-App mit npm install und npm run ios -- --simulator="iPhone SE 3" und untersuche anschließend RCTUITextField.mm um Zeile 216 sowie RCTUITextView.mm im Bereich der Zeilen 369–378. Vergleiche das Verhalten mit aktiviertem caretHidden und überprüfe die Metal-Logs, während das Feld fokussiert ist. Als erledigt gilt die Aufgabe, wenn die fortlaufenden Fehler Surface 1073741823 x 1073741823 is too large bei dem reproduzierten iOS TextInput-Fall nicht mehr auftreten.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
ios, objective-c, react-native
Bereich
mobile
Issue-Typ
Bug
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Aktiv
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
68/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.