-
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 #11768] mWeb-lands on wrong screen when pressing the back button from the attachment screen @gadhiyamanan #11372
Comments
Triggered auto assignment to @alexpensify ( |
Assigning to Engineering for the check if this one should be closed or give it another review. cc: @roryabraham and @stitesExpensify |
Triggered auto assignment to @cristipaval ( |
Hmm so the problem is that the attachment picker is not really a new page, it's the same page with a modal on it, so the back button is technically functioning correctly. IMO this is not a bug, it's user error. If they hit the |
If we do want to fix this, we could artificially add the report page a second time to react-navigation, but that could also cause problems where the flow is:
So we would need to artificially add it when you click "add attachment" and then remove it when you hit the "x". Again I think that's not worth it though, happy to hear other opinions |
Looks like something related to As a reminder, please make sure that all proposals are not workarounds and that any and all attempt to fix the issue holistically have been made before proceeding with a solution. Proposals to change our Feel free to drop a note in #expensify-open-source with any questions. |
cc @puneetlath because this is react-navigation related I'm thinking we should put it on HOLD pending the FT you're working on |
removed the assignment since I see you guys are already triaging it. Thanks! |
Putting this on HOLD and added to tracking issue: https://github.com/Expensify/Expensify/issues/221853 (sorry, this tracking issue is internal) |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
Triggered auto assignment to @slafortune ( |
Switching out the weekly for monthly given that the navigation project is large and has no ETA. |
Still on hold for the navigation project. |
Same same. |
Still on hold. |
Still on hold |
Coming off hold very soon! |
This is not its own screen so I dont think this will be fixed and I am not sure if we should be fixing it in terms of consistency wit desktop. There the attachment is also a modal and not its own page. |
Ok cool, still aiming to get to this one this week. |
Still trying to make time. Low priority. |
Re-tested and this is now fixed. |
@gadhiyamanan I just sent you an offer for reporting. Once you've accepted and been paid, we can close this one out. |
@JmillsExpensify offer accepted, thanks! |
Anytime. All paid out! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
Should navigate to chat screen
Actual Result:
Navigate to home screen
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: 1.2.8.0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers): any
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Screen_Recording_20220913_134105_Chrome.mp4
Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1663057441323579
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: