[Tracking] Active navigational issues

[parasharrajat]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

I have started to notice a couple of navigation issues. Creating this issue to help us better manage those and track their solutions.

List of issues

• [$500] Different behavior for mobile and mWeb when user opens an attachment and tries to go back - Reported by @thesahindia #7010
• [HOLD for payment 2022-03-08] [$500] Account details stuck in RHN when switching chats #6720
• [HOLD for payment 2022-03-22] [$1,000] Back arrow on chat doesn't work after decreasing the browser size - Reported by @Tushu17 #7091
• [HOLD for payment 2022-03-17] [$1000] Report a bug does not lead to Concierge - Reported by Hitesh  #6908 ⌛
• [HOLD] mWeb - Chrome start page opens tapping back button from chat window #7618
• [HOLD #11768] [$16000] Desktop - The Back ⌘[ and Forward ⌘] shortcuts keys are not working as expected in LHN #4612
• [$1000] After completing "Request money" journey the chat randomly redirects to other chat Reported by @mananjadhav #6912 ⌛
• Opening a unknown report from the URL displays a blank chat page and no error - Reported by: @parasharrajat #5897
• [$500] Different behavior for mobile and mWeb when user opens an attachment and tries to go back - Reported by @thesahindia #7010

Platform:

Where is this issue occurring?

• Web
• iOS
• Android
• Desktop App
• Mobile Web

Version Number:
Reproducible in staging?:
Reproducible in production?:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:

View all open jobs on GitHub

[MelvinBot]

Triggered auto assignment to @MitchExpensify (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

[MitchExpensify]

Thanks @parasharrajat, tracking issue looks good. I don't think any further triage action is required of me but let me know if you think otherwise

[parasharrajat]

made progress on the list.

[MelvinBot]

This issue has not been updated in over 14 days. eroding to Weekly issue.

[MelvinBot]

This issue has not been updated in over 14 days. eroding to Weekly issue.

[MelvinBot]

This issue has not been updated in over 14 days. eroding to Weekly issue.

[MelvinBot]

This issue has not been updated in over 14 days. eroding to Weekly issue.

[MelvinBot]

This issue has not been updated in over 14 days. eroding to Weekly issue.

[MelvinBot]

This issue has not been updated in over 14 days. eroding to Weekly issue.

[MelvinBot]

This issue has not been updated in over 14 days. eroding to Weekly issue.

[MelvinBot]

This issue has not been updated in over 14 days. eroding to Weekly issue.

[MelvinBot]

This issue has not been updated in over 14 days. eroding to Weekly issue.

[MelvinBot]

This issue has not been updated in over 14 days. eroding to Weekly issue.

[parasharrajat]

Steadily making progress on issues one by one.... @MitchExpensify could you please assign me this issue so that Melvin does not close it.?

[mountiny]

Assigned Rajat

[parasharrajat]

Moving up...

[parasharrajat]

Shhhh.....Melvin

[mountiny]

Do you want to make this Monthly since it is a tracking issue?

[parasharrajat]

Yeah that would be great. Thanks @mountiny

[marcaaron]

Just curious, how many of these fixes have happened in the react-navigation repo? How many would we say are "workarounds"? And if we worked around something was there some justification as to why documented somewhere?

[marcaaron]

@parasharrajat I'm going to close this and move all related issues into a GitHub project for now if you see any issues related to navigation please grab me.

[parasharrajat]

Thank you for collaborating on these. This was much needed.