[Due for payment 2025-03-24] iOS&Android - Help panel - Keyboard does not dismiss when help panel is opened

[IuliiaHerets]

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

---

Version Number: 9.1.9-1
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: iPhone 15 Pro Max / iOS 18.3
App Component: Chat Report View

Action Performed:

Precondition:

• Help panel feature is enabled by switching language to Spanish and back to English.

1. Launch ND or hybrid app.
2. Open any chat.
3. Tap on the composer to open keyboard.
4. Tap help icon.

Expected Result:

Keyboard will dismiss.

Actual Result:

Keyboard does not dismiss.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6761693_1741170040743.ScreenRecording_03-05-2025_18-16-48_1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @laurenreidexpensify

[melvin-bot]

Triggered auto assignment to @laurenreidexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

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

[melvin-bot]

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

[github-actions]

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

[mjasikowski]

caused by #56490, but a minor UI bug, so not a blocker

[mjasikowski]

assigning @blazejkustra as the original PR author

[quinthar]

Given that this is only visible to explicit internal testers, and doesn't impact anyone who isn't a tester, I don't think this should be a deploy blocker.

[blazejkustra]

Yep, this shouldn't be a deploy blocker. Thanks for confirming!

[melvin-bot]

@mjasikowski, @blazejkustra, @laurenreidexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

[laurenreidexpensify]

@blazejkustra can you confirm when you'll have a fix up by? Thanks

[blazejkustra]

This week I'll be focusing on fixing all help pane issues, hopefully EOW

[289Adam289]

Hi, I am Adam from SWM and I am helping @blazejkustra with help pane issue. I'd like to work on this one.

[mjasikowski]

@289Adam289 assigning to you as well

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

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

• Render tooltip only when help pane is hidden #58104

If no regressions arise, payment will be issued on 2025-03-24. 🎊

For reference, here are some details about the assignees on this issue:

• @blazejkustra does not require payment (Contractor)
• @289Adam289 does not require payment (Contractor)

[melvin-bot]

@mjasikowski @laurenreidexpensify @blazejkustra / @289Adam289 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[melvin-bot]

Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.

[laurenreidexpensify]

BugZero Checklist:

• [Contributor] Classify the bug:

Bug classification

Source of bug:

• 1a. Result of the original design (eg. a case wasn't considered)
• 1b. Mistake during implementation
• 1c. Backend bug
• 1z. Other:

Where bug was reported:

• 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
• 2b. Reported on staging (eg. found during regression or PR testing)
• 2d. Reported on a PR
• 2z. Other:

Who reported the bug:

• 3a. Expensify user
• 3b. Expensify employee
• 3c. Contributor
• 3d. QA
• 3z. Other:

• [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

  Link to comment:

• [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

  Link to discussion:

• [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

Regression Test Proposal Template

• [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

  Link to issue:

Regression Test Proposal

Precondition:

Test:

Do we agree 👍 or 👎

[laurenreidexpensify]

@blazejkustra can you complete checklist thanks

[blazejkustra]

@laurenreidexpensify Hey! What checklist exactly? Does it matter that I'm from an agency? I've never done that before 😅

[blazejkustra]

I think @brunovjk was reviewing this as a C+

[brunovjk]

@laurenreidexpensify This issue is part of some regressions during the implementation of Help Panel. I think we can follow the payment on the original issues.

[laurenreidexpensify]

Okay thanks @brunovjk

[brunovjk]

I can't reproduce this anymore after implementing this PR. Tested on 27 Mar v9.1.20-2 Develop. We can close, payment and BZ checklist will be handled here. Thanks!