mWeb- Chat - Keyboard not opening when editing message.

[kbecciv]

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

---

Issue found when executing PR #19477

Action Performed:

1. Go to URL https://staging.new.expensify.com/
2. Open any conversation.
3. Long press on the message.
4. Press on the edit message.
5. Input should be focused, and the keyboard should appear.

Expected Result:

The keyboard should open automatically when the message changes.

Actual Result:

Keyboard not opening when editing message.

Workaround:

Unknown

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.18.1

Reproducible in staging?: yes

Reproducible in production?: yes

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

https://platform.applause.com/services/links/v1/external/778f3baa67dffd2d70747df8fbee6af3a8c7b4277154fa0676da50cc2032d71a

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @jliexpensify (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

[jliexpensify]

Hi @PauloGasparSv and @fedirjh - @kbecciv has indicated this is an issue associated with your PR: #19477

Do you mind taking a look at this? Cheers!

[fedirjh]

@jliexpensify That PR introduced a change that affects IOS native. The reported platform is IOS Safari. So I am sure this is not related to that PR.

I think this issue is existing before that PR . @terrysahaidak can you take a look ?

[terrysahaidak]

Yes, the PR introduces the .native file instead of .android file, so the web should not be affected.

Also the root cause of the bug was related to the bug (or feature, since they made the same behavior on both iOS and Android) in the implementation of react-native-modal.

But on the web we don't use react-native-modal.

I'll take a look at what exactly is causing this.

[Victor-Nyagudi]

I'm currently experiencing this bug on Android native too.

[terrysahaidak]

I'm currently experiencing this bug on Android native too.

What phone and version of the app do you use? Is it in production?

[Victor-Nyagudi]

This happened in DEV against the staging server.

• Phone: Samsung Galaxy A14
• App version: v1.3.18-2

[jliexpensify]

@Victor-Nyagudi can you try logging onto staging instead? I'm on v1.3.19-2 (Pixel 3a, Chrome) and can't repro - the keyboard pops up and I can edit properly:

[Victor-Nyagudi]

It's working fine in staging on mobile web, @jliexpensify .

By the way, is there a staging/production app for mobile (iOS and Android)?

The one from the play store seems to be the same as the one installed when running npm run android.