Emoji picker keyboard is covering compose box reported by @aneequeahmad

[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. open web app on browser of phone(or android/IOS app).
2. Open any report and focus on composer to open soft keyboard.
3. Press emoji picker option/icon on keyboard.

Expected Result:

Composer should be above the keyboard emoji picker and shouldn't hide behind the keyboard as if keyboard is closed

Actual Result:

Composer is hiding behind the keyboard

Workaround:

unknown

Platform:

Where is this issue occurring?

• iOS
• Android
• Mobile Web

Version Number: 1.2.21-4

Reproducible in staging?: Need reproduction

Reproducible in production?: Need reproduction

Email or phone of affected tester (no customers):

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

Notes/Photos/Videos:

emoji-picker-keyboard-bug.mp4

22-11-08-18-43-39.mp4

Expensify/Expensify Issue URL:

Issue reported by: @aneequeahmad

Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1667091893014729

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

[sketchydroide]

I was not able to replicate this on version 1.2.25-0, not sure if this was fixed in the mean time, or if it was just on this ocasion.
CCing @tgolen as this might be related to the Keyboard Avoidance features, this would definetly be something to look for on regular iOS developement and a typical issue with keyboard and fields, not sure how that translates to RN.

[tgolen]

I think this is a duplicate of #10609 which was closed because it was no longer reproducable. I think if we can consistently reproduce this in some fashion, then we should reopen the original issue.

[sketchydroide]

I could not reproduce myself, it seemed to work just fine, and this GH was opened with the version of 4 versions ago
@kavimuru can you try to reproduce again on the latest version?

[kavimuru]

@sketchydroide Our team and I were not able to reproduce the issue on different devices.

[sketchydroide]

it's a weird one, particularly that it popped out again, but I think we can close this, and if it happens a third time then reoppen the original one #10609.
Do you agree @tgolen?

[melvin-bot]

@sketchydroide, @mateocole Whoops! This issue is 2 days overdue. Let's get this updated quick!

[sketchydroide]

will close this one, next time we reopen the original one