[iOS 26] App crashes on startup with TurboModule performVoidMethodInvocation - SIGABRT
### Description ## Description React Native app crashes immediately on startup on iOS 26.1, but works perfectly on iOS 18.x. The crash occurs in `ObjCTurboModule::performVoidMethodInvocation` with a SIGABRT signal. This appears to be related to the known issue discussed in [reactwg/react-native-new-architecture#276](https://github.com/reactwg/react-native-new-architecture/discussions/276), where `performVoidMethodInvocation` doesn't properly handle NSExceptions thrown by TurboModules. ## Expected behavior App should launch normally, as it does on iOS 18.x. ## Actual behavior App crashes with SIGABRT before reaching JavaScript execution. ## Environment - React Native: 0.81.5 - Expo SDK: 54.0.27 - New Architecture: Enabled (required by react-native-reanimated 4.x) - iOS versions tested: - iOS 26.1 (iPhone 17 Pro): ❌ CRASH - iOS 18.6 (Simulator iPhone 16 Pro): ✅ WORKS - Xcode: 17C48 ## Crash Log ``` Incident Identifier: F20BB16E-E4D2-4192-8527-AE827EF146D2 Hardware Model: iPhone18,1 Process: Krimp [6640] Version: 1.1.3 (9) OS Version: iPhone OS 26.1 (23B85) Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: SIGNAL 6 Abort trap: 6 Triggered by Thread: 7 Thread 7 Crashed: 0 libsystem_kernel.dylib pthread_kill + 8 1 libsystem_pthread.dylib pthread_kill + 268 (pthread.c:1721) 2 libsystem_c.dylib abort + 124 (abort.c:122) 3 libc++abi.dylib abort_message + 132 (abort_message.cpp:66) 4 libc++abi.dylib demangling_ter
Posted by JoffreyTrebot on Dec 11, 2025, 4:33 PM
Tags
Related issues
- Many devs love to shit on the guy from the 'I just want the exe.
- Now imagine how poor people stress if their smartphone bricks or gets damaged or lost.
- Resuming an extended-thinking session fails permanently with 400 "thinking blocks cannot be modified" (transcript stores thinking text as empty but keeps signat
- I'll preface this with a statement that as a European I want European alternatives to succeed, and MS-owned GitHub to shrivel and disappear.
- Yeah, but there’s a world of difference between “not perfect” and “we rounded a few sliders, and now the modal is a nightmare to use”.
- I used to write a lot of native Windows corporate software in the 90's and 2000's and my standard login window was a floating draggable o...
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
reliability (SaaS)
Many devs love to shit on the guy from the 'I just want the exe.
Now imagine how poor people stress if their smartphone bricks or gets damaged or lost.
Resuming an extended-thinking session fails permanently with 400 "thinking blocks cannot be modified" (transcript stores thinking text as empty but keeps signat
I'll preface this with a statement that as a European I want European alternatives to succeed, and MS-owned GitHub to shrivel and disappear.
Yeah, but there’s a world of difference between “not perfect” and “we rounded a few sliders, and now the modal is a nightmare to use”.
I used to write a lot of native Windows corporate software in the 90's and 2000's and my standard login window was a floating draggable o...
App broken with Mosquitto broker 7.0.0
[BUG] Remote Control: automatic reconnection doesn't work -- connection drops silently with no recovery
[iOS 26] App crashes on startup with TurboModule performVoidMethodInvocation - SIGABRT
### Description ## Description React Native app crashes immediately on startup on iOS 26.1, but works perfectly on iOS 18.x. The crash occurs in `ObjCTurboModule::performVoidMethodInvocation` with a SIGABRT signal. This appears to be related to the known issue discussed in [reactwg/react-native-new-architecture#276](https://github.com/reactwg/react-native-new-architecture/discussions/276), where `performVoidMethodInvocation` doesn't properly handle NSExceptions thrown by TurboModules. ## Expected behavior App should launch normally, as it does on iOS 18.x. ## Actual behavior App crashes with SIGABRT before reaching JavaScript execution. ## Environment - React Native: 0.81.5 - Expo SDK: 54.0.27 - New Architecture: Enabled (required by react-native-reanimated 4.x) - iOS versions tested: - iOS 26.1 (iPhone 17 Pro): ❌ CRASH - iOS 18.6 (Simulator iPhone 16 Pro): ✅ WORKS - Xcode: 17C48 ## Crash Log ``` Incident Identifier: F20BB16E-E4D2-4192-8527-AE827EF146D2 Hardware Model: iPhone18,1 Process: Krimp [6640] Version: 1.1.3 (9) OS Version: iPhone OS 26.1 (23B85) Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: SIGNAL 6 Abort trap: 6 Triggered by Thread: 7 Thread 7 Crashed: 0 libsystem_kernel.dylib pthread_kill + 8 1 libsystem_pthread.dylib pthread_kill + 268 (pthread.c:1721) 2 libsystem_c.dylib abort + 124 (abort.c:122) 3 libc++abi.dylib abort_message + 132 (abort_message.cpp:66) 4 libc++abi.dylib demangling_ter
Comments (0)
No comments yet. Start the discussion.