[$500] Request - Participant deep link opens Participant page briefly and keyboard opens in Scan

[lanitochka17]

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: 1.3.88-3
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
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Issue found when executing PR #26149

Action Performed:

Precondition: Make sure Scan tab is selected when Request money tab is opened

1. Navigate to https://staging.new.expensify.com/
2. Paste the link https://staging.new.expensify.com/request/new/participants/
   in chat
3. Tap on the link

Expected Result:

User is redirected to Request money selector page without opening Participants page and keyboard

Actual Result:

The link opens Participants page briefly with keyboard showing up. Sometimes Participants page is not shown but keyboard still appears

Workaround:

Unknown

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Android: Native

Bug6245643_1697905602424.Screen_Recording_20231021_205927_New_Expensify__2_.mp4

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~014061867ab191f52d
• Upwork Job ID: 1715778155199119360
• Last Price Increase: 2023-11-18

[melvin-bot]

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

[melvin-bot]

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

[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

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @abdulrahuman5196 (External)

We already have #26538 to remove support for money request deep links.
I believe the issue would not invalid after these changes, we should hold this issue.
Can you please confirm if this would be still valid issue after planned changes under #26538 ? @hayata-suenaga

[hayata-suenaga]

can you check if the refactoring issue is really removing the deep link? If I remember correctly, I think @tgolen is making change in a way that still supports deep linking to money-request related pages

You are right, looks like we are doubling down on supporting money requests as I read discussion further. my bad.
In that case, We can continue to investigate further. Thanks @hayata-suenaga !

[benomatis]

Proposal

Please re-state the problem that we are trying to solve in this issue.

If Scan option is originally selected (where the keyboard is not normally needed), coming there using a Participant deep link opens the keyboard briefly.

What is the root cause of that problem?

With the introduction of the autoFocus prop in BaseOptionsSelector.js, which appears to have originally aimed to fix a focus issue in web and desktop (relevant commits: 4c478d3, 90b96de, f45b2ca, 7ff6e00, 0d2d560, 70beac8, 5d28fdb, 5788291), the relevant platform specific constraint ([CONST.PLATFORM.DESKTOP, CONST.PLATFORM.WEB].includes(getPlatform())) to allow this.textInput.focus() to execute inside setTimeout was only introduced in componentDidUpdate and is missing from componentDidMount.

What changes do you think we should make in order to solve the problem?

The same platform specific constraint ([CONST.PLATFORM.DESKTOP, CONST.PLATFORM.WEB].includes(getPlatform())) should be introduced in componentDidMount to this.textInput.focus() inside setTimeout.

What alternative solutions did you explore? (Optional)

NA

Additional note

Note that shouldDelayFocus in src/components/OptionsSelector/index.android.js could be removed as part of this change as it appears to be unnecessary, it's not being used in BaseOptionsSelector.js at all.

Also note that I could not reproduce the part where the participant list appeared briefly first, but I do believe this solution should resolve the issue of the keyboard unnecessarily opening in that case as well, otherwise it should probably be investigated as a separate issue.