-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[$500] [HOLD for payment 2024-03-26] [Simplified Collect][Categories] - App crashes when selecting categories and editing category name at the same time #38404
Comments
👋 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:
|
Triggered auto assignment to @amyevans ( |
@amyevans FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
We think that this bug might be related to #wave-control |
Production: bandicam.2024-03-15.17-47-23-854.mp4 |
@FitseTLT are you able to reproduce on production? Looks like you pointed out PR which was deployed to production 2 weeks ago as offending one. |
I think disabling editing of a category when it is selected is more appropriate or use a key other than category name that does not change when a category name is changed. cc: @ArekChr @luacmartins |
Looks like the ability to edit was introduced in #37969. @ArekChr @luacmartins is this featured behind a beta? Wondering if we can demote. And can I assign y'all to work on the fix? |
We can demote this since it's available only on |
Upon checking the crash log, this looks to be the same root cause as #38379 (comment) |
Discussed this one internally and we actually wanna deselect all categories when we're editing one. PR up - #38416 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.54-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-03-26. 🎊 |
Gonna close this one since it was a regression from #38379 (comment) and no payment is due. |
hii @luacmartins I reviewed the PR #38416 can you please repopen for payment 🙇 |
Triggered auto assignment to @miljakljajic ( |
Oh sorry, missed that one. Reopening to process payment |
Job added to Upwork: https://www.upwork.com/jobs/~0197c3d60db95d1c51 |
Current assignee @ishpaul777 is eligible for the External assigner, not assigning anyone new. |
@ishpaul777 please accept the upwork offer! |
paid! |
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: 1.4.53-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:
Precondition:
Expected Result:
App does not crash
Actual Result:
App crashes
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6415046_1710514615236.20240315_224432.mp4
log.txt
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: