Thanks. Here’s more context. This is a React Native/Expo iOS app distributed through TestFlight. When a user taps Connect to Apple Health, the app checks isHealthDataAvailableAsync(), requests read-only HealthKit access for steps, sleep, and HRV, checks getRequestStatusForAuthorization(), and then reads step statistics, sleep samples, and HRV samples. The crash was reported during the Connect flow, but I haven’t isolated which of those calls triggers it. The report is from app version 1.0.0 (build 12) on iOS 26.6.1. It shows EXC_CRASH / SIGABRT on com.meta.react.turbomodulemanager.queue; the last exception backtrace ends in ObjCTurboModule::performVoidMethodInvocation. The report does not include the original exception name or reason, a HealthKit error code, or the specific native method. The main-thread stack shows an activity indicator being drawn, but it is not the faulting thread. A previous build’s stack showed UIKit feedback-generator frames. I removed the haptic call from the Apple Health screen as a test, but I haven’t independently verified that the build 12 binary includes that change; build 12’s report does not show haptic-generator frames. I don’t yet have a symbolicated report. Can this backtrace identify the native caller, and what specific symbolicated report or other diagnostic would help determine which HealthKit call is failing? Before attaching the .ips publicly, redact device identifiers and any personal or account details. The crash summary above is safe to post without the full raw report.