search

Expensify / App

Welcome to New Expensify: a complete re-imagination of financial collaboration, centered around chat. Help us build the next generation of Expensify by sharing feedback and contributing to the code.
https://new.expensify.com
MIT License
3.48k stars 2.83k forks source link

iOS Hybrid - Composer - Keyboard does not reopen after dismissing the context menu #50830

Open lanitochka17 opened 15 hours ago

lanitochka17 commented 15 hours ago

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

Version Number: 9.0.49-0 Reproducible in staging?: Y Reproducible in production?: N If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Email or phone of affected tester (no customers): applausetester+kh081006@applause.expensifail.com Issue reported by: Applause - Internal Team

Action Performed:

  1. Launch New Expensify app
  2. Go to DM
  3. Send a message
  4. With keyboard up, long press on the message
  5. Tap outside the context menu

Expected Result:

The keyboard will reopen after dismissing the context menu (production behavior and staging mweb behavior)

Actual Result:

The keyboard does not reopen after dismissing the context menu

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/user-attachments/assets/261b4b34-4ad6-4d0a-9459-c84a777221ae

View all open jobs on GitHub

melvin-bot[bot] commented 15 hours ago

Triggered auto assignment to @flodnv (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

melvin-bot[bot] commented 15 hours ago

💬 A slack conversation has been started in #expensify-open-source

github-actions[bot] commented 15 hours ago

:wave: 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.
marcaaron commented 14 hours ago

Reproducible in production?: Y

So, not a blocker right?

lanitochka17 commented 13 hours ago

sorry, my mistake. Reproducible in production?: N