[Workspace Feeds] App crashes after enabling Expensify Card

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.34-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace settings.
3. Go to More features.
4. Enable Expensify Card.

Expected Result:

App will not crash.

Actual Result:

App crashes after enabling Expensify Card.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1309.txt

Bug6601797_1726194038264.crahs.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @twisterdotcom (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @jasperhuangg (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.

[koko57]

I can look at this, as I worked on EC
cc @trjExpensify @mountiny but should it be a deploy blocker? It's not in beta anymore?

[VickyStash]

Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue.

[VickyStash]

The app crashes with the next error:

'cards_-1_Expensify Card' key can't be changed to 'cards_18317771_Expensify Card'. useOnyx() only supports dynamic keys if they are both collection member keys from the same collection e.g. from 'collection_id1' to 'collection_id2'.

It looks like we have the similar issue opened related to useOnyx crash: Investigate useOnyx crash when changing policy_-1 key to policy__FAKE_

[twisterdotcom]

@mountiny - can we just assign @VickyStash or @koko57 here? Definitely feels like a blocker. cc @kevinksullivan

[trjExpensify]

It's still in beta. 👍

[luacmartins]

If this is on a beta, I'll remove the blocker

[VickyStash]

The PR which fixes the crash is opened for the review: #49173

[VickyStash]

I'm going to be OOO Sept 14-22, in case the PR won't be merged @koko57 will take care of it.

[mountiny]

The fix worked well, merged it

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[mountiny]

The onyx PR was merged so now @fabioh8010 will test the onyx bump on this bug

[trjExpensify]

Any reason this is still open?

[twisterdotcom]

Do I need to pay out @s77rt?

[trjExpensify]

I think that was handled in the other issue for Fabio's PR.

The PR for this issue didn't get C+: #49173