Android - App crashes when tapping back arrow on request money screen

[isagoico]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Expected Result:

App should work without any issues

Actual Result:

App crash only when tapping the back arrow.

Action Performed:

1. Launch the app
2. Log in with expensifail account
3. Select any user
4. Click on Plus button and select Request Money
5. Put any amount and Click Next
6. In Field What's it for? - put some text
7. Tap on back arrow twice.

Workaround:

Unknown

Platform:

Where is this issue occurring?

Web
iOS
Android ✔️
Desktop App
Mobile Web

Version Number: 1.0.36-0

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos:

Video

Expensify/Expensify Issue URL:

View all open jobs on Upwork

[MelvinBot]

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

[isagoico]

Another issue affecting the IOU beta this time only on android, marking as deploy blocker. @Julesssss if you disagree this should be a DB please go ahead and remove the label :)

[Julesssss]

Thanks, @isagoico. Removing the blocker label as it isn't a common flow yet.

[Julesssss]

Confirmed the crash is occurring on Android, no matter if the comment is set or not.

Web is showing a console error at the same place if you quickly navigate back through the steps. Not convinced this is related, but it's the best guess I have currently.

Native device logs aren't helpful, but leaving them here anyway:

[Julesssss]

This also occurs if you request money from a chat (skipping the participants step), so I'm marking the above comment as outdated.

[MelvinBot]

Triggered auto assignment to @puneetlath (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

[Julesssss]

On Second thoughts, we'll leave the IOI blockers internal. Please ignore the label :)

[marcaaron]

I can reproduce this pretty easily gonna take a stab at it.

[marcaaron]

It seems the crash only happens when the software keyboard is open.

[marcaaron]

Using InteractionManager.runAfterInteractions() seems to fix this. Dismissing the keyboard and navigating to the previous step seems to be too much for Android to handle.

[marcaaron]

Ah ha. I think it is caused by the dismiss behavior of the screen

https://reactnavigation.org/docs/stack-navigator/#keyboardhandlingenabled

Since the back button is in the left gutter for where the "swipe" occurs the keyboard is dismissed but then reappears when we are transitioning to the next view and then 💥

Fix incoming.