You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-07-21] Track distance - GPS - App Crashed when tap on start button #95876
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
Crash type: iOS native EXC_BREAKPOINT (SIGTRAP) on the main thread, entirely inside the Expensify binary (native frames, no JS backtrace). From the attached .ips: "type":"EXC_BREAKPOINT","signal":"SIGTRAP", build_version 9.4.33.1, os_version iPhone OS 26.5.1.
Only reproducible in staging (9.4.33), not production (9.4.32) — so a change in the 9.4.33 deploy introduced it.
The Start button path is native-location heavy. Tapping Start runs startLocationUpdatesAsync(...) (expo-location) which registers with expo-task-manager, and the iOS permissions flow calls checkLocationAccuracy():
This PR is the only change in this deploy that touches the native location stack. package.json diff (9.4.32-3..9.4.33-1-staging):
react-native0.83.1 → 0.85.3
expo55.0.25 → 56.0.8 (SDK 55 → 56)
expo-location55.1.10 → 56.0.15
expo-task-manager55.0.2 → 56.0.16
expo-modules-core55.0.25 → 56.0.14, hermes-compiler bumped, plus a full ios/Podfile.lock rebuild.
A native EXC_BREAKPOINT in exactly the location-tracking flow, appearing right after a major RN + Expo SDK bump, points at an incompatibility/assertion in the upgraded expo-location / expo-task-manager native code (e.g. the background location task registration on iOS).
Lower-likelihood candidate
The GPS feature's own JS barely changed this cycle — the only direct edits to IOURequestStepDistanceGPS/ were delegateAccountID threading (part of durable-receipts, #94950). That's pure JS and would not produce a native EXC_BREAKPOINT, so it's unlikely to be the cause.
Suggested next steps
Symbolicate the attached .ips against the 9.4.33.1 dSYM to confirm the trap is inside expo-location/expo-task-manager.
If confirmed, treat #92484 as the deploy blocker and loop in @war-in.
Activity
applause-bot commentedon Jul 11, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/fbde84d4e7a588611e4c3f95986d3b76391bca198083342caf53c1d0483c7006
https://platform.applause.com/services/links/v1/external/575c9b6b384ebf63e9d49656b7628837a43147fe4168eca5c016271a343d250c
https://platform.applause.com/services/links/v1/external/e8b4b8880ec0d84be159a0f0cb9f1c6a2029063d6d8f6190ff218592416fb1f2
melvin-bot commentedon Jul 11, 2026
Triggered auto assignment to @neil-marcellini (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jul 11, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jul 11, 2026
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
MelvinBot commentedon Jul 11, 2026
Run details
neil-marcellini commentedon Jul 12, 2026
(Neil's AI agent)
Analysis: likely cause of the GPS Start crash
What we observe (evidence)
EXC_BREAKPOINT (SIGTRAP)on the main thread, entirely inside theExpensifybinary (native frames, no JS backtrace). From the attached.ips:"type":"EXC_BREAKPOINT","signal":"SIGTRAP",build_version 9.4.33.1,os_version iPhone OS 26.5.1.startLocationUpdatesAsync(...)(expo-location) which registers with expo-task-manager, and the iOS permissions flow callscheckLocationAccuracy():src/pages/iou/request/step/IOURequestStepDistanceGPS/GPSButtons/index.tsx→initLocationTracking→startLocationUpdatesAsyncsrc/pages/iou/request/step/IOURequestStepDistanceGPS/BackgroundLocationPermissionsFlow/index.ios.tsx→checkLocationAccuracyPrime suspect
Upgrade React Native to 0.85.3 (#92484) by @war-in, merged 2026-07-09, shipped in 9.4.33.
This PR is the only change in this deploy that touches the native location stack.
package.jsondiff (9.4.32-3..9.4.33-1-staging):react-native0.83.1 → 0.85.3expo55.0.25 → 56.0.8 (SDK 55 → 56)expo-location55.1.10 → 56.0.15expo-task-manager55.0.2 → 56.0.16expo-modules-core55.0.25 → 56.0.14,hermes-compilerbumped, plus a fullios/Podfile.lockrebuild.A native
EXC_BREAKPOINTin exactly the location-tracking flow, appearing right after a major RN + Expo SDK bump, points at an incompatibility/assertion in the upgradedexpo-location/expo-task-managernative code (e.g. the background location task registration on iOS).Lower-likelihood candidate
The GPS feature's own JS barely changed this cycle — the only direct edits to
IOURequestStepDistanceGPS/weredelegateAccountIDthreading (part of durable-receipts, #94950). That's pure JS and would not produce a nativeEXC_BREAKPOINT, so it's unlikely to be the cause.Suggested next steps
.ipsagainst the 9.4.33.1 dSYM to confirm the trap is insideexpo-location/expo-task-manager.neil-marcellini commentedon Jul 12, 2026
@war-in could you please help us fix this one?
jakubstec commentedon Jul 13, 2026
hey, i'm from software mansion, expert agency and I will help fixing that.
21 remaining items
melvin-bot commentedon Jul 23, 2026
@jakubstec Whoops! This issue is 2 days overdue. Let's get this updated quick!
jakubstec commentedon Jul 24, 2026
can be closed
melvin-bot commentedon Jul 27, 2026
@jakubstec Whoops! This issue is 2 days overdue. Let's get this updated quick!
jakubstec commentedon Jul 28, 2026
pr with a fix has been merged
melvin-bot commentedon Jul 31, 2026
@jakubstec Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
melvin-bot commentedon Aug 4, 2026
@jakubstec Still overdue 6 days?! Let's take care of this!
jakubstec commentedon Aug 5, 2026
can be closed