-
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
[HOLD for payment 2023-10-23] [HOLD for payment 2023-10-23] [HOLD for payment 2023-10-20] [HOLD for payment 2023-10-20] [$500] iOS native - App crashes when going back on a Manual request #29114
Comments
Current assignee @trjExpensify is eligible for the Bug assigner, not assigning anyone new. |
Bug0 Triage Checklist (Main S/O)
|
Job added to Upwork: https://www.upwork.com/jobs/~01426d1c07ab30e760 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @aimane-chnaif ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.App crashes when going back on a Manual request What is the root cause of that problem?This error happen on all devices, not only native mobiles. What changes do you think we should make in order to solve the problem?Lines 2274 to 2276 in 8d42ad3
This function reset all request info and go to input screen again. We need to call secondResetMoneyRequestInfo instead of resetMoneyRequestInfo
Result Screen.Recording.2023-10-09.at.11.10.49.PM.movScreen.Recording.2023-10-09.at.11.11.49.PM.movWhat alternative solutions did you explore? (Optional) |
ProposalPlease re-state the problem that we are trying to solve in this issue.App crashes when going back on a Manual request What is the root cause of that problem?App/src/components/OptionsSelector/BaseOptionsSelector.js Lines 73 to 75 in 8d42ad3
Because of calling focus of null. What changes do you think we should make in order to solve the problem?We can add check logic there and this works very well on my side.
What alternative solutions did you explore? (Optional) |
@aimane-chnaif lets prioritize this one as its important flow in coming 2 weeks. thanks! |
ProposalPlease re-state the problem that we are trying to solve in this issue.There are 2 issues here
As first bug is dupe of #28129, I will provide root cause & solution only for 2nd bug here What is the root cause of that problem?Participants selector screen uses App/src/components/OptionsSelector/BaseOptionsSelector.js Lines 73 to 76 in d916eff
What changes do you think we should make in order to solve the problem?We already have clear logic here App/src/components/OptionsSelector/BaseOptionsSelector.js Lines 136 to 139 in d916eff
|
I can confirm that navigation bug was unintentionally fixed in #27936. |
Triggered auto assignment to @AndrewGable, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@aimane-chnaif I think that this crash will not happened if that navigation is fixed. |
@yh-0218 I faced this many times on the pages where options list is used. We should fix that bug Here's another reproducible step: click Search icon and Esc key at the same time Screen.Recording.2023-10-10.at.6.14.54.AM.mov |
@hungvu193 no, it's different bug |
Actually both of it crashed because of the timeout wasn't cleared. I also pointed it out in comment here: |
Seems like the main purpose of that GH is different from this one - #28318 (comment) |
It was first created to resolve the console error (which because of the timeout), however while discussing it, @iwiznia pointed out that, we also need to display the NotFoundView instead of do nothing while clicking the deeplink., so I updated the proposal to cover 2 cases.
So the issue (#28318) can cover this one. Anyway I think let hear other thoughts from @iwiznia and @fedirjh |
👋 @iwiznia & @fedirjh we haven't really got time to dally on this issue if it's not the same root cause. It's a crash in the middle of the request money flow, and it's going live to TU on Tuesday. Can you check the above, please? In the meantime, @AndrewGable can you put your thoughts on this so we're ready to move forward if we need to. |
@aimane-chnaif It's the same bug initially reported in #28318 @trjExpensify I agree with @hungvu193 that this has the same root cause as #28318 , Also this solution is the same as what @hungvu193 has suggested in #28318 (comment) |
This is what I suggest as this seems like urgent, #28318 is non-urgent. No need to waste time arguing because of issue conflict. If #28318 will be fixed quickly (in a day or so), go ahead and close this one. I just found another crash case on split bill. |
Yeah, I think we need to get a PR up to fix this crash in the request money flow today, especially if it's also in the split bill case. I like the idea of using this issue to fix the crash with the above solution, and #28318 to introduce this "no page found" blocking form in the scenario being discussed there. @mountiny do you agree? We need to resolve this pretty urgently. |
Coming from Slack thread here, going to assing @hungvu193 as their solution was proposed earlier albeit on different issue. it was related. |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.84-10 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 2023-10-23. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
This comment was marked as duplicate.
This comment was marked as duplicate.
@AndrewGable, @trjExpensify, @hungvu193, @aimane-chnaif Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Can we get the checklist filled out please, @aimane-chnaif? Also, not sure why 4 checklists got triggered. 😅 |
This is already added in guideline - https://github.com/Expensify/App/blob/main/contributingGuides/STYLE.md#how-do-i-auto-focus-a-textinput-using-usefocuseffect |
https://expensify.slack.com/archives/C01GTK53T8Q/p1698059102119519 😄 |
Okay, so confirming payments as follows:
#urgency bonus applied as per here. |
Settled up! |
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: v1.3.79-3
Reproducible in staging?: Y
Reproducible in production?:
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: @MitchExpensify
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1696874025934959
Action Performed:
Expected Result:
App doesn't 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?
Screenshots/Videos
Android: Native
Android: mWeb Chrome
iOS: Native
RPReplay_Final1696873974.mov
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: