[Awaiting Payment] [$250] [Native Share] iOS - Share file - Referral banner and share button are hidden behind the keyboard

[nlemma]

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.18-0
Reproducible in staging?: Yes
Reproducible in production?: No
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: #58834
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: Other

Action Performed:

1. Open a photo from device gallery.
2. Tap Share.
3. Select Expensify.
4. Go to Share.
5. Select a user.
6. Tap on the message field.

Expected Result:

In Step 4, referral banner will appear above the keyboard (this is the app behavior when submitting expense from FAB).
In Step 5, share button will move to above the keyboard.

Actual Result:

In Step 4, referral banner is hidden behind the keyboard.
In Step 5, share button is hidden behind the keyboard.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6780964_1742854506642.ScreenRecording_03-25-2025_05-40-37_1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021924487053519886813
• Upwork Job ID: 1924487053519886813
• Last Price Increase: 2025-05-19

Issue Owner

Current Issue Owner: @

[melvin-bot]

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

[melvin-bot]

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

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

[nlemma]

@garrettmknight FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[grgia]

Self assigning as this is part of native share. This one is a blocker as it prevents the user from sharing @289Adam289

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[grgia]

I don't think we need the referral banner in the share modal, will need confirmation

[grgia]

Native Share Deploy Blocker Slack Thread

[289Adam289]

Hi, I am Adam from SWM I was working on Share Extension pr and I'd like to work on this issue.

[grgia]

Demoting this one too

[melvin-bot]

This issue has not been updated in over 15 days. @garrettmknight, @grgia, @shubham1206agra, @289Adam289 eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

[shubham1206agra]

@garrettmknight The PR was deployed long ago. You can progress with payment here.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021924487053519886813

[melvin-bot]

Current assignee @shubham1206agra is eligible for the External assigner, not assigning anyone new.

[garrettmknight]

@shubham1206agra can you complete the checklist and I'll pay out?

[shubham1206agra]

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: https://github.com/Expensify/App/pull/55748/files#r2096010434

• [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: Not Required

• [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.

• [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

Test:

1. Open a photo from device gallery.
2. Tap Share.
3. Select Expensify.
4. Go to Share.
5. Verify that referral banner appears above the keyboard.
6. Select a user.
7. Verify that Share button will move to above the keyboard.
8. Tap on the message field.

Do we agree 👍 or 👎

[garrettmknight]

Payment Summary:

• Contributor: @shubham1206agra $250 via NewDot