iOS Expense - App crashes when unselecting category after disabling all categories

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.0.25-11
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4897807
Email or phone of affected tester (no customers): applausetester+kh050806@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat
3. Submit at least two expenses with category
4. Go to workspace settings > Categories
5. Disable all the categories
6. Go back to workspace chat
7. Go to transaction thread (any expense in Step 3)
8. Click Category
9. Tap on the selected category

Expected Result:

App will not crash

Actual Result:

App crashes when unselecting category in transaction thread after disabling all categories

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6585435_1724856920344.ScreenRecording_08-28-2024_22-50-02_1.mp4

logs (2).txt

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @Gonals (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[github-actions]

👋 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:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[lanitochka17]

We think that this bug might be related to #wave-collect - Release 1

[Gonals]

Tested a few times and I haven't been able to reproduce the crash. @cristipaval also gave it a shot and it worked for him in an actual device, so closing for now

[IuliiaHerets]

The issue is still reproducible, build - v9.0.26-3

RPReplay_Final1724962422.MP4

[Gonals]

I still can't reproduce it. Is it a specific device?

[IuliiaHerets]

No, as a minimum 2 testers can repro this issue in the different devices

[Gonals]

Was this tested on physical devices or on the simulator? In either case, which models were used?

[Gonals]

Tried to reproduce again on a few different simulated devices to no avail. Closing.