[HOLD for payment 2022-12-08] Android -Chat - The compose field is covered by keyboard

[kavimuru]

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

---

Action Performed:

1. Launch app > go to any chat
2. Start to enter message

Expected Result:

The message field should be fully visible if the keyboard was open.

Actual Result:

The message field is hidden if the keyboard was open.

Workaround:

unknown

Platform:

Where is this issue occurring?

• Android

Version Number: 1.2.33-1
Reproducible in staging?: y
Reproducible in production?: n
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

Bug5839913_az_recorder_20221128_165302.mp4

Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

View all open jobs on GitHub

[OSBotify]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Triggered auto assignment to @roryabraham (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[0xmiros]

This will be fixed by #13106

[roryabraham]

@luacmartins I don't know if we want to wait for #13106, but looking through the checklist I think the only change that might've caused this is #12988

[mananjadhav]

I am not sure if #12988 can cause the regression, as the code only removes one placeholder. No other change.

[0xmiros]

After deep research, I finally found that #12642 caused regression.
Especially, this change:

-       StatusBar.setTranslucent(true);

But I think this is a good solution to fix another related issues so I don't recommend to revert this.

#13106 will fix all of the related issues along with this GH.

Let me list again the issues this PR will fix:
#10483
#10609
#11087
#12592
#12622
#13111
#13152

cc: @tgolen @roryabraham @mountiny @pecanoro @iwiznia @Julesssss (since you were assigned one of the related issues or PRs)

[mountiny]

Great investigation and fix @0xmiroslav 🙇

[Julesssss]

Confirmed this is resolved by this PR.

[Julesssss]

The solution here is to have the PR reviewed asap to unblock the deploy.

[luacmartins]

This is fixed by #13106, closing!

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.34-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• fix android keyboard issue #13106

If no regressions arise, payment will be issued on 2022-12-08. 🎊

After the hold period, please check if any of the following need payment for this issue, and if so check them off after paying:

• External issue reporter
• Contributor that fixed the issue
• Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

• Merged PR within 3 business days of assignment - 50% bonus
• Merged PR more than 9 business days after assignment - 50% penalty