[Pay reporting bonus] App crashes when collapsing composer after returning back to app

[kavimuru]

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:

1. Go to any chat,
2. Type at least three lines of text,
3. Expand composer,
4. Go to home screen or switch to other app
5. Return to New Expensify app
6. Collapse composer from expanded state

Expected Result: Composer box

should collapse

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?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.20-3
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
Notes/Photos/Videos: Any additional supporting documentation

Crash.mp4

az_recorder_20230530_151835.1.mp4

Expensify/Expensify Issue URL:
Issue reported by: @nishancx
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1685293536816139

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @strepanier03 (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[allroundexperts]

There's an existing PR that fixes this #19809

[strepanier03]

Thank you @allroundexperts! I was able to recreate so I'll follow along for the PR close.

[strepanier03]

PR still open so on hold for now.

[strepanier03]

PR was deployed to Prod yesterday so I tested again and can confirm the behavior no longer happens for me.