You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Expense-User not directed to scan receipt flow when opening via app short cut. #100246
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.
👋 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:
Identify the pull request that introduced this issue and revert it.
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
Staging only, not production. Production is 9.4.68-1, staging is 9.4.69-0. Comparing the two branches gives 129 changed files.
No App-side change can explain this. Filtering that 129-file diff for anything touching deep links, navigation, linking config, routes, screens, startup, IOU/scan flows, or native code returns only version bumps:
src/ROUTES.ts, src/SCREENS.ts, src/libs/Navigation/**, src/DeepLinkHandler.tsx and src/libs/Navigation/linkingConfig/subscribe.ts are byte-identical between production and staging.
The Android static shortcuts are native.Expensify/App's own Android manifest declares no android.app.shortcuts meta-data and no static shortcut resource; the only shortcut code in the App repo is ShortcutManagerUtils / ShortcutManagerModule, which pushes dynamic per-conversation shortcuts for notifications (new-expensify://r/<reportID>) — not the "Receipt" launcher shortcut. Precedent: [Due for payment 2026-07-16] [$250] Android: SmartScan shortcut re-navigates when already on SmartScan screen #88009 was explicitly filed as a follow-up to a Mobile-Expensify trampoline-activity PR, confirming the static "SmartScan"/"Receipt" shortcut lives on the native side.
The report's "BrowserStack" field on this issue also links to Mobile-Expensify#14097, which is consistent (though on its own it is not proof — that field is free text).
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:
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).
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.
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
Activity
applause-bot commentedon Sep 3, 2026
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
melvin-bot commentedon Sep 3, 2026
Triggered auto assignment to @inimaga (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Sep 3, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Sep 3, 2026
👋 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:
MelvinBot commentedon Sep 3, 2026
🔍 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/AppPR 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/Appdiff for9.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.
DeployBlockerCashis kept — this ships as part of the App/HybridApp deploy and is not reproducible on production.DeployBlockerwas not present, so nothing was removed.📋 Detailed Analysis
Evidence
Staging only, not production. Production is
9.4.68-1, staging is9.4.69-0. Comparing the two branches gives 129 changed files.No App-side change can explain this. Filtering that 129-file diff for anything touching deep links, navigation, linking config, routes, screens, startup, IOU/scan flows, or native code returns only version bumps:
android/app/build.gradle(9.4.66-0→9.4.69-0)ios/NewExpensify/Info.plist,ios/NotificationServiceExtension/Info.plist,ios/ShareViewController/Info.plistMobile-Expensify(submodule pointer)src/ROUTES.ts,src/SCREENS.ts,src/libs/Navigation/**,src/DeepLinkHandler.tsxandsrc/libs/Navigation/linkingConfig/subscribe.tsare byte-identical between production and staging.I reviewed the changed-file list of every App PR on the checklist (79837: LHN - Report Remains Marked as Unread After Returning Online Despite Message Being Read Offline #94738, [No QA] Docs updates for E/A#96990 Copy workspace settings help article #97145, Move pre-selected assignee to top of list in Issue New Expensify Card flow #98131, [No QA] Docs updates for E/A#96169 alternate route selection for distance expenses #98472, [No QA] Docs updates for E/A#97853 Add Canadian Multiple Tax Export template #98478, Remove OnyxUtils.get() from OnyxDerived init (use connectWithoutView) #99004, Show the report-level rejected message in the expense report preview #99124, [No QA] Docs updates for E/A#97883 Document Send to someone for tracked expenses #99130, Always open the Export submenu on Search, even with a single export option #99217, [NoQA] prevent SVG definitions from re-rendering on every commit #99669, refactor: thread onboarding status into openReport for report pages #99685, Remove the walletConnectionStatus beta #99754, Add link to home address message #99767, [NO QA] Update CONTRIBUTING.md #99981, Treat an explicit $0.00 max expense amount as configured, not unset #99994, Open invoice child reports in the wide RHP from the X replies link #100017, [No QA] Pass authtoken back through SignInUser #100084, [NO QA] Travel billing: Update bank account setup copy #100106, [No QA] Add images to Expensify Card articles #100116, [Payment due @ahmedGaber93] [No QA] Rename originalUseOnyx to useOnyxWithoutSnapshots #100200, [No QA] Fix monthly NextStepUtils test determinism #100205, [BC] [No QA] Add Business Central beta and basic commands #100210). They are docs updates, Search/Onyx refactors, workspace-rules, wallet, sign-in and Business Central changes. None of them touches a file involved in launching or routing an Android app shortcut.
The Android static shortcuts are native.
Expensify/App's own Android manifest declares noandroid.app.shortcutsmeta-data and no static shortcut resource; the only shortcut code in the App repo isShortcutManagerUtils/ShortcutManagerModule, which pushes dynamic per-conversation shortcuts for notifications (new-expensify://r/<reportID>) — not the "Receipt" launcher shortcut. Precedent: [Due for payment 2026-07-16] [$250] Android: SmartScan shortcut re-navigates when already on SmartScan screen #88009 was explicitly filed as a follow-up to a Mobile-Expensify trampoline-activity PR, confirming the static "SmartScan"/"Receipt" shortcut lives on the native side.The only native delta is Update version to 1.2.50-10 on staging #14097. Production carries Mobile-Expensify
f384b694; staging carries3ac8c5c1. On the checklist the content-bearing bump isUpdate Mobile-Expensify submodule to cb8902a, attributed to Mobile-Expensify#14097; every later bump (9.4.66-1,9.4.67-0,9.4.68-0,9.4.68-1,9.4.69-0) is a version bump. Update version to 1.2.50-10 on staging #14097 is also the sole entry under Mobile-Expensify PRs in Deploy Checklist: New Expensify 2026-09-02 #100228.The report's "BrowserStack" field on this issue also links to Mobile-Expensify#14097, which is consistent (though on its own it is not proof — that field is free text).
Verification
src/libs/Navigation/linkingConfig/subscribe.ts(which contains the/scanskip-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) andsrc/DeepLinkHandler.tsx.src/ROUTES.ts,src/SCREENS.tsandsrc/libs/Navigation/linkingConfig/config.ts, are unchanged betweenproductionandstaging— confirmed via the branch comparison, and the last change tosubscribe.ts(2026-08-31) is already live in production.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-0is 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:
/scandeep-link path and its skip-rule are unchanged, so a changed path or an unexpected trailing segment/query would silently no-op).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-cb8902acommit and re-cutting9.4.69.view run
TaduJR commentedon Sep 3, 2026
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
mitarachim commentedon Sep 3, 2026
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
TaduJR commentedon Sep 3, 2026
Not able to repro again and again.
@AndrewGable Can you repro this on latest main?
war-in commentedon Sep 3, 2026
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 stagingI verified on the latest main and everything works fine
1 remaining item
melvin-bot commentedon Sep 3, 2026
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.
melvin-bot commentedon Sep 3, 2026
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.
TaduJR commentedon Sep 3, 2026
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?
war-in commentedon Sep 3, 2026
@TaduJR checking 👀
war-in commentedon Sep 3, 2026
Interesting, after adding your change, it's reproducible 🤔
TaduJR commentedon Sep 3, 2026
Confusing a little. I will investigate it then.
Thanks @war-in
inimaga commentedon Sep 3, 2026
The suspect PR is being reverted https://github.com/Expensify/Mobile-Expensify/pull/14100
Once it gets CPd, let's retest again.
AndrewGable commentedon Sep 3, 2026
Asked for a retest here: https://expensify.slack.com/archives/C09V78U42D8/p1788449573581099
IuliiaHerets commentedon Sep 3, 2026
Not repro. Build v9.4.69-1
screen-20260903-195320-1788454395532.mp4
inimaga commentedon Sep 4, 2026
Thanks for confirming. @TaduJR Please keep this blocker in mind for the follow-up PR.