-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[HOLD for payment 2024-01-31] [$500] Android - IOU-App crashes on request money with new user on deleting request. #33800
Comments
Job added to Upwork: https://www.upwork.com/jobs/~017ebef5d4acfc8b7d |
Triggered auto assignment to @sakluger ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @aimane-chnaif ( |
📣 @rashidkarim11! 📣
|
ProposalPlease re-state the problem that we are trying to solve in this issue.App crashes on request money with new user on deleting request. What is the root cause of that problem?the App/src/components/ReportActionItem/MoneyRequestView.js Lines 344 to 352 in f2b74e8
Here is the error log: ![]() What changes do you think we should make in order to solve the problem?Inside the transaction object, we need to add a default value for the
to key: ({report, parentReportActions = {}}) => { OR alternativly we can use App/src/components/MoneyRequestHeader.js Lines 179 to 186 in 9208c95
POCScreen.Recording.2023-12-31.at.12.13.53.AM.mov |
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
This looks like a duplicate of #33295 so I am going to close in favor of that one. The only difference is the platform, but the behavior is exactly the same. @abzokhattab if you think your proposal will solve the other issue, could you please repost your proposal on #33295? Thanks! |
@sakluger I am not able to reproduce the other issue lets see if it's fixed we can open this one again ..
not really .. the attached video there shows "hmm it's not here" page not a compiler error as it's currently happening in android |
@sakluger @aimane-chnaif Hey again, the other issue is not reproducible anymore and got closed ... however the current issue is still reproducible again i believe the two issues are different, here we have a compiler error in anrdroid not |
@sakluger @aimane-chnaif @izarutskaya Just a reminder, the other issue is closed and still, this one is reproducible on the latest build (v1.4.22-3): Screen.Recording.2024-01-08.at.5.17.45.PM.mov |
@sakluger let's re-open |
@abzokhattab I have one more case of crash (check video for repro step). Happening on Proposal: #33800 (comment) ![]() Screen.Recording.2024-01-15.at.3.31.12.PM.mov🎀 👀 🎀 C+ reviewed |
Triggered auto assignment to @cristipaval, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
📣 @aimane-chnaif 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @abzokhattab 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
Thanks @aimane-chnaif for flagging the other crash as well! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.30-1 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-01-31. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Hey @aimane-chnaif, can you please complete the BZ checklist so I can close the issue out after payment tomorrow? Thanks! |
|
All paid out, thanks everyone! |
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: 1.4.20-2
Reproducible in staging?: Y
Reproducible in production?: Y
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: Applause-Internal Team
Slack conversation: @
Action Performed:
Expected Result:
App must not crash on request money with new user on deleting request.
Actual Result:
App crashes on request money with new user on deleting request.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6328968_1703921841380.crash.mp4
log crash.txt
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: