Skip to content

Expense-User not directed to scan receipt flow when opening via app short cut. #100246

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: V9.4.69
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://github.com/Expensify/Mobile-Expensify/pull/14097
Email or phone of affected tester (no customers): dreamnitethedragon+vegst@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redmi note 10s android 13
App Component: Money Requests

Action Performed:

Pre-condition: logged in
1.Launch app
2. Long press app and select receipt

Expected Result:

User must be directed to scan receipt flow when opening via app short cut.

Actual Result:

User not directed to scan receipt flow when opening via app short cut.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7249633_1788400963849.Screenrecorder-2026-09-03-07-26-39-886.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7249633

Activity

  1. applause-bot commented on Sep 3, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/1698c8a961d789ae9b64b50f33a888fabcf6f44fe7f385adb234bdaf0dc1b279

  2. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 3, 2026
  3. melvin-bot commented on Sep 3, 2026

    @melvin-bot

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

  4. melvin-bot commented on Sep 3, 2026

    @melvin-bot

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

  5. github-actions commented on Sep 3, 2026

    @github-actions
    Contributor

    👋 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.
  6. MelvinBot commented on Sep 3, 2026

    @MelvinBot
    Contributor

    🔍 Investigation Summary

    Classification: Frontend bug (native Android / HybridApp — the fix is not in Expensify/App)
    Causing PR: Mobile-Expensify#14097 (Medium confidence) — the only native change in this release. No Expensify/App PR on this checklist can cause this.
    Related Issues: #88009 (previous Android static-shortcut regression, also rooted in Mobile-Expensify), #94821

    Recommendation: NEEDS INVESTIGATION

    The Android launcher ("force touch") shortcuts are defined and dispatched natively — there is no shortcut, deep-link, navigation, routing or scan-flow change anywhere in the Expensify/App diff for 9.4.69-0, so this cannot have come from an App PR. The only native delta between production (9.4.68-1) and staging (9.4.69-0) is the Mobile-Expensify submodule bump that brought in #14097, which needs to be checked by its owners; if there's no quick fix, rolling the submodule pointer back is the way to unblock the deploy.

    Assigned: none — the causing change is in Mobile-Expensify and I can't resolve its author/reviewers from here. Please pull in the author and reviewers of Mobile-Expensify#14097.
    Labels: No changes. DeployBlockerCash is kept — this ships as part of the App/HybridApp deploy and is not reproducible on production. DeployBlocker was not present, so nothing was removed.

    📋 Detailed Analysis

    Evidence

    Verification

    • Affected surface: the Android launcher shortcut → NewDot scan tab hand-off. On the App side the receiving code is src/libs/Navigation/linkingConfig/subscribe.ts (which contains the /scan skip-rule added by Fix: SmartScan shortcut re-navigates when already on SmartScan screen #90782 for [Due for payment 2026-07-16] [$250] Android: SmartScan shortcut re-navigates when already on SmartScan screen #88009) and src/DeepLinkHandler.tsx.
    • Both files, plus src/ROUTES.ts, src/SCREENS.ts and src/libs/Navigation/linkingConfig/config.ts, are unchanged between production and staging — confirmed via the branch comparison, and the last change to subscribe.ts (2026-08-31) is already live in production.
    • Conversely, the Mobile-Expensify submodule pointer is part of this staging diff, and it is the only thing in the diff that can change how the launcher shortcut behaves.
    • No live App test was run: this reproduces only through an Android launcher shortcut, which the web test surface for this run cannot exercise.

    Root Cause

    I cannot state the exact defect, because the native shortcut implementation is not in this repo and I do not have read access to it — that part of the investigation has to happen on the Mobile-Expensify side.

    What is established with high confidence is the location: the intent that the "Receipt" launcher shortcut fires (and the hand-off it performs into the NewDot scan tab) is produced natively, and the only change to that code in 9.4.69-0 is Mobile-Expensify#14097. The App-side receiver is unchanged from the version that works in production, so either the shortcut's intent/target URL changed shape, or the hand-off no longer reaches the deep-link handler at all.

    Two concrete things worth checking first on the native side:

    1. Whether the URL the shortcut emits still matches the routes the App resolves to the scan tab (the App's /scan deep-link path and its skip-rule are unchanged, so a changed path or an unexpected trailing segment/query would silently no-op).
    2. Whether the trampoline/launch path regressed such that the intent is consumed before the deep link is delivered.

    Since the fix is outside Expensify/App, I am deliberately not proposing any App code change. The unblock options are (a) a native fix in Mobile-Expensify, or (b) reverting Mobile-Expensify#14097 / rolling the submodule pointer back to the pre-cb8902a commit and re-cutting 9.4.69.


    view run

  7. TaduJR commented on Sep 3, 2026

    @TaduJR
    Contributor

    Not able to repro on my end

    Screen.Recording.2026-09-03.at.7.21.34.AM.mov

    @mitarachim Could you double check this one?

    Thanks

  8. mitarachim commented on Sep 3, 2026

    @mitarachim

    Hello @TaduJR , I still could reproduce issue using build v9.4.69-0.
    my device : samsung A54/android 16

    2026-09-03.11.28.35.AM.mp4
  9. TaduJR commented on Sep 3, 2026

    @TaduJR
    Contributor

    Not able to repro again and again.

    @AndrewGable Can you repro this on latest main?

  10. war-in commented on Sep 3, 2026

    @war-in
    Contributor

    Hi! I worked on some deeplinks refactors recently

    Such regression could be caused by those PRs, but both passed QA and were deployed to prod.
    I wonder if this regression could be caused by the tester having two Expensify apps installed on their phone. Also, please make sure that in the phone settings -> Apps -> Expensify -> Defaults (Set as default) section -> Supported web addresses, all links are marked as handled. They are by default on prod, but can be turned off on staging

    I verified on the latest main and everything works fine

  11. 1 remaining item

  12. melvin-bot commented on Sep 3, 2026

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

  13. melvin-bot commented on Sep 3, 2026

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

  14. TaduJR commented on Sep 3, 2026

    @TaduJR
    Contributor

    Thanks so much for the info @war-in

    Do you think it's related to https://github.com/Expensify/Mobile-Expensify/pull/14097

    It just got reverted. Can you repro with the above PR one line change?

  15. war-in commented on Sep 3, 2026

    @war-in
    Contributor

    @TaduJR checking 👀

  16. war-in commented on Sep 3, 2026

    @war-in
    Contributor

    Interesting, after adding your change, it's reproducible 🤔

  17. TaduJR commented on Sep 3, 2026

    @TaduJR
    Contributor

    Confusing a little. I will investigate it then.

    Thanks @war-in

  18. inimaga commented on Sep 3, 2026

    @inimaga
    Contributor

    The suspect PR is being reverted https://github.com/Expensify/Mobile-Expensify/pull/14100

    Once it gets CPd, let's retest again.

  19. AndrewGable commented on Sep 3, 2026

    @AndrewGable
    Contributor
  20. IuliiaHerets commented on Sep 3, 2026

    @IuliiaHerets

    Not repro. Build v9.4.69-1

    screen-20260903-195320-1788454395532.mp4
  21. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Sep 3, 2026
  22. inimaga commented on Sep 4, 2026

    @inimaga
    Contributor

    Thanks for confirming. @TaduJR Please keep this blocker in mind for the follow-up PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions