Repository navigation
[HOLD https://github.com/Expensify/App/issues/102514] [Sentry: APP-JB3] HybridApp iOS AVCaptureSession stopRunning crash still active after #97103 #99850
Description
Sentry
https://expensify.sentry.io/issues/APP-JB3
Impact (snapshot at filing)
- Users (last 14d): 25
- Events (last 14d): 25
- Last seen: ongoing, fired within the hour of filing
- Platform: iOS HybridApp
- Mechanism:
nsexception - Culprit:
CameraSession.checkIsActive
Release breakdown over the last 14 days, production only:
| Release | Users |
|---|---|
| 9.4.53-10 | 4 |
| 9.4.57-3 | 4 |
| 9.4.60-2 | 3 |
| 9.4.51-1 | 3 |
| 9.4.56-3 | 2 |
| 9.4.59-5 | 2 |
| 9.4.55-4 | 2 |
| 9.4.61-4 | 1 |
| 9.4.58-4 | 1 |
| 9.4.44-6 | 1 |
Why this is a new issue rather than a comment
[Sentry: APP-JB3] HybridApp iOS AVCaptureSession stopRunning during CameraSession.configure
tracked this signature and was closed and paid on 2026-08-25. The crash did not stop. It is spread
across ten production releases in the current window, including 9.4.61-4 and 9.4.60-2, so it is not
confined to old builds that predate the fix.
Error
NSGenericException: *** -[AVCaptureSession stopRunning] stopRunning may not be called between
calls to beginConfiguration and commitConfiguration
Suspected cause
stopRunning is reached while a configuration transaction is still open, so the session is torn down
between beginConfiguration and commitConfiguration. The culprit moved from
CameraSession.configure in the earlier report to CameraSession.checkIsActive, which suggests the
guard added for the configure path does not cover the activity check path, or that the two run
concurrently on different queues.
Reproduction
Unknown — see the events linked from the Sentry issue. Backgrounding or dismissing the receipt
scanner while the camera is still configuring is the most likely trigger given the throw site.
Related
- Prior issue, closed and paid: App#97103
- Parent tracker: Top Sentry crashes monthly check-in
Issue Owner
Current Issue Owner: @suneoxMetadata
Metadata
Assignees
Type
Projects
- Status
Activity
melvin-bot commentedon Sep 2, 2026
@mountiny Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Sep 3, 2026
@mountiny Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
melvin-bot commentedon Sep 3, 2026
@mountiny Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
melvin-bot commentedon Sep 3, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @brunovjk (
External)melvin-bot commentedon Sep 3, 2026
Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue.
brunovjk commentedon Sep 8, 2026
Should we seek for proposals here, @mountiny? Thanks.
44 remaining items
[-][Sentry: APP-JB3] HybridApp iOS AVCaptureSession stopRunning crash still active after #97103[/-][+][HOLD https://github.com/Expensify/App/issues/102514] [Sentry: APP-JB3] HybridApp iOS AVCaptureSession stopRunning crash still active after #97103[/+]melvin-bot commentedon Oct 6, 2026
@ZhenjaHorbach Huh... This is 4 days overdue. Who can take care of this?
melvin-bot commentedon Oct 8, 2026
@ZhenjaHorbach 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
melvin-bot commentedon Oct 12, 2026
@ZhenjaHorbach 10 days overdue. I'm getting more depressed than Marvin.
ZhenjaHorbach commentedon Oct 13, 2026
Not overdue
@suneox already has a fix
@mountiny
Let's assign @suneox to this issue!
suneox commentedon Oct 14, 2026
@mountiny I think this assignment was meant for #102742. That's the one where I reproduced the crash and proposed the
PageNavigatorfix in Slack, this issue is on hold for the V5 upgrade. Could you assign me to #102742? Thanks!ZhenjaHorbach commentedon Oct 14, 2026
Oh
Sorry
I'm stupid
Wrong issue 😂
yusufdeveloper2903 commentedon Oct 19, 2026
@mountiny Hi! Just to clarify the status here: ZhenjaHorbach approved my proposal (#99850 (comment)) right before the decision to move to V5, and the issue went on hold before I was assigned.
Since my fix lived in the V4 patch that #102898 removes, I understand there is no frontend/native work left here and this issue is only for confirming that APP-JB3 stops after V5 ships. Is that right?
melvin-bot commentedon Oct 19, 2026
@suneox Huh... This is 4 days overdue. Who can take care of this?