-
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
[$250] Task – App crashes when click on assignee in existing task #49514
Comments
Triggered auto assignment to @alexpensify ( |
Triggered auto assignment to @flodnv ( |
👋 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:
|
ProposalPlease re-state the problem that we are trying to solve in this issue.App crashes What is the root cause of that problem?The report is used before it's initialize App/src/pages/tasks/TaskAssigneeSelectorModal.tsx Lines 123 to 129 in 4c9a3fb
What changes do you think we should make in order to solve the problem?Update this to get the report data from
What alternative solutions did you explore? (Optional)Or we can move the navigate logic to another
|
Why did this just start happening upon this deploy? What PR caused this? |
This is from #49241 See slack thread: https://expensify.slack.com/archives/C01GTK53T8Q/p1726837086718439?thread_ts=1726822044.310019&cid=C01GTK53T8Q |
Updated #49241 cc @luacmartins |
This is not the offending PR. I tried reverting it locally, and I'm still able to reproduce the bug. |
Thanks @nkdengineer. @rojiphil @BrtqKr can you please check if #48325 caused this? |
@flodnv, I don't think this would be related. Seems like accessing report from task is making this work
currently, the memo is accessing itself and it seems to be the reason, why this bug is occurring, but this is quite surprising because it's been working like this for a while somehow
|
Right, it is strange. I assigned you @nkdengineer |
📣 @jjcoffee 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @nkdengineer 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
Thanks, will raise the PR soon. |
Thanks! |
Awesome, now we wait for this one to go to Prouduction. |
Retest was a pass 🎉 Recording.2024-09-23.115241.mp4Checking it off the list. |
Flagging that automation failed, and it was deployed to production on 09-24. |
Ugh, automation failed and the payment date should have been yesterday. I'll work on the payment process tomorrow. |
Regression Test Proposal
Do we agree 👍 or 👎 |
I think this will be caught during regular regression tests, since we have many tests on tasks. |
Payouts due: 10-01-2024
Upwork job is here. |
Closing - I believe that I sent the payment via Upwork, but something looks off in Upwork. Please reply if you didn't get the payment and I'll fund the new job I sent your way. I'll return later to complete the regression test. |
@alexpensify I didn't receive any payment, just the notification that the contract has ended and weirdly another about accepting an offer (I've accepted this). |
@alexpensify Same for me, the job just closed without payment. I accepted the new 2nd offer though, it can be paid out there. |
Thanks for these updates! There is an issue an Upwork that is being investigated to address the payment process. I'm going to hold until there is a fix. Convo: https://expensify.slack.com/archives/C01GTK53T8Q/p1728319262830679 |
@jjcoffee and @nkdengineer, our team figured out the Upwork bug, and I tried to complete the payment via another payment path in Upwork. Their support team is working on a permanent fix for the bug. I'd really appreciate it if you could confirm today's payment sent successfully under the new contract. Thanks! |
@alexpensify Yes it was sent for me 💯 Thanks! |
Me too, thank you! |
Awesome, thanks for hanging in there with me. This bug is a wild one on the Upwork side. |
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: v9.0.39-0
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/4989792
Email or phone of affected tester (no customers): applausetester+jpcategory_2@applause.expensifail.com
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
Assignee list opens
Actual Result:
App crashes
Workaround:
Unknown
Platforms:
Screenshots/Videos
2009.txt
Bug6609721_1726820372331.Assignee_crash.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: