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
[$500] Hold request - App crashes when saving a reason during hold request flow #36831
Version Number: 1.3.43-0 Reproducible in staging?: y Reproducible in production?: new feature If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by: applasue internal team Slack conversation:
Action Performed:
Launch New Expensify app.
Create a manual request from any user.
Go to request details page.
Click 3-dot menu > Hold request.
Add a reason and save it.
Expected Result:
App does not crash.
Actual Result:
App crashes.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
changed the title [-]Hold request - App crashes when saving a reason during hold request flow[/-][+][$500] Hold request - App crashes when saving a reason during hold request flow[/+]on Feb 20, 2024
👋 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.
@joekaufmanexpensify I have discussed this internally. You may close this issue as I am keeping track of payment internally and will ask to pay once the issue is resolved. Just write in the payment summary that I have not been paid yet.
Activity
[-]Hold request - App crashes when saving a reason during hold request flow[/-][+][$500] Hold request - App crashes when saving a reason during hold request flow[/+]melvin-bot commentedon Feb 20, 2024
Job added to Upwork: https://www.upwork.com/jobs/~0126f2cd8c5ade674d
melvin-bot commentedon Feb 20, 2024
Triggered auto assignment to @joekaufmanexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Feb 20, 2024
Triggered auto assignment to Contributor-plus team member for initial proposal review - @shubham1206agra (
External)github-actions commentedon Feb 20, 2024
👋 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:
24 remaining items
joekaufmanexpensify commentedon Mar 25, 2024
Discussing further here.
shubham1206agra commentedon Mar 27, 2024
@joekaufmanexpensify I have discussed this internally. You may close this issue as I am keeping track of payment internally and will ask to pay once the issue is resolved. Just write in the payment summary that I have not been paid yet.
joekaufmanexpensify commentedon Apr 1, 2024
Sounds good. TY! LMK when your Upwork situation is all set, and I'll re-open this and pay you.
shubham1206agra commentedon Apr 17, 2024
@joekaufmanexpensify You can process payment here now.
shubham1206agra commentedon Apr 23, 2024
@joekaufmanexpensify Bump here.
joekaufmanexpensify commentedon Apr 23, 2024
Awesome. TY!
joekaufmanexpensify commentedon Apr 23, 2024
OG upwork job is closed, so opened new one: https://www.upwork.com/jobs/~01456ff2950adec042
joekaufmanexpensify commentedon Apr 23, 2024
@shubham1206agra offer sent for $500!
shubham1206agra commentedon Apr 23, 2024
@joekaufmanexpensify Accepted
joekaufmanexpensify commentedon Apr 23, 2024
@shubham1206agra $500 sent and contract ended!
joekaufmanexpensify commentedon Apr 23, 2024
Upwork job closed.
joekaufmanexpensify commentedon Apr 23, 2024
All set.