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
Android - Switch to Expensify Classic navigates to mWeb OD instead of stays in app #100256
Version Number: 9.4.69-0 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): N/A Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Samsung Galaxy A52 / Android 14 App Component: User Settings
Action Performed:
Preconditions: user already signed in to any account
Steps:
Open the Expensify app
Navigate to Account -> Troubleshoot
Tap Clear cache and restart until "Switch to Expensify Classic" displayed and tap on it
Expected Result:
After tapping "Switch to Expensify Classic", user navigate to OD and stays in native app
Actual Result:
in some devices after tapping "Switch to Expensify Classic", it redirects to mWeb, but in some other devices nothing happened after tapping “Switch to Expensify Classic” and unable to reach OD
👋 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.
changed the title [-]Android-Switch to Expensify Classic navigates to mWeb OD instead of stays in app[/-][+]Android - Switch to Expensify Classic navigates to mWeb OD instead of stays in app[/+]on Sep 3, 2026
Classification: Frontend bug (client-side — mobile/HybridApp native layer, not an App JS regression) Causing PR: No Expensify/App PR in this release touches this code path. The only change in production...staging that can affect it is the Mobile-Expensify submodule bump f72dc07 → 3ac8c5c (Medium confidence), which carries https://github.com/Expensify/Mobile-Expensify/pull/14097 — the same PR referenced in this bug report. Related Issues: #100246 (also Android-app-only, also staging-only, also filed against the same Mobile-Expensify PR build), #100228 (StagingDeployCash)
Recommendation: NEEDS INVESTIGATION
Every App-side file in the "Switch to Expensify Classic" path is byte-identical between production and staging, so no App PR on this checklist can be reverted to fix this; the change has to be on the native/HybridApp side. Someone with Mobile-Expensify access needs to confirm whether the changes in that release (notably PR #14097) affect HybridApp native module registration / OldDot launch, and revert there if so.
Assigned: no assignee change — the causing change appears to be in Mobile-Expensify and I do not have access to that repo, so I cannot identify the author or approving reviewers to assign. Please loop in the author of Mobile-Expensify#14097. Labels: No changes. DeployBlockerCash is kept — the App/Android deploy really is broken and the issue is not reproducible in production. DeployBlocker was not present, so nothing was removed. Nothing here points at a backend/API fix.
📋 Detailed Analysis
Verification
The full production...staging diff for this release is 129 files. None of them is in the "Switch to Expensify Classic" path:
src/pages/settings/Troubleshoot/TroubleshootPage.tsx — unchanged (last touched 2026-08-12, already in production)
modules/hybrid-app/** (the JS↔native bridge, including the Android Kotlin module) — 0 files changed in this release
package.json — only the version field changed (9.4.66-0 → 9.4.69-0); @expensify/react-native-hybrid-app is file:./modules/hybrid-app and was not bumped
android/app/build.gradle — only versionCode/versionName
I also checked the non-obvious candidates that could perturb Onyx loading state, since this flow is gated on it: src/hooks/useOnyx.ts (rename-only refactor, originalUseOnyx → useOnyxWithoutSnapshots), src/setup/index.ts (removed one RAM-only key), src/libs/actions/Session/index.ts (2FA authToken param), src/libs/Network/SequentialQueue.ts (offline comment/read-time handling). None of them touch NVP_TRY_NEW_DOT, CONFIG.IS_HYBRID_APP, or the redirect.
The only remaining delta that reaches this behaviour is the submodule pointer:
HybridApp branch: TroubleshootPage.tsx#L133-L136 → closeReactNativeApp({shouldSetNVP: true, isTrackingGPS}) (stays in the native app)
Non-HybridApp branch: TroubleshootPage.tsx#L137-L143 → switchToOldDot('') + openOldDotLink(CONST.OLDDOT_URLS.INBOX, true) (opens OldDot in the browser, i.e. mWeb)
…which is a straight pass-through to the native module (modules/hybrid-app/src/index.native.ts#L6-L8). The implementation shipped in this repo for Android is the standalone stub that hard-codes false (ReactNativeHybridApp.kt#L12-L14), and its closeReactNativeApp is a no-op log (L20-L22). The real implementation comes from the mobile build, so this JS behaves entirely according to what the native layer reports.
That maps cleanly onto the two reported symptoms, and explains why they differ per device/build:
"redirects to mWeb" — isHybridApp() resolving to false at runtime, so the standalone branch runs and openOldDotLink(..., true) opens Classic in the browser (TroubleshootPage.tsx:141). This is also consistent with the item being visible in that state: with shouldRespectMobileLock === false, the visibility gate no longer hides the item while tryNewDot is still loading (TryNewDotUtils.ts#L36-L42).
"nothing happens / can't reach OD" — the HybridApp branch running, but the exit being swallowed before it reaches native (HybridApp/index.ts#L103-L124), or the native closeReactNativeApp not launching OldDot.
Reproducibility supports a native-side cause: staging-only, production-unaffected, Android app only, while the App JS for this flow is identical to production. Two separate Android-only blockers on this checklist (this one and #100246, an app-shortcut/deep-link entry point) were both filed against the same Mobile-Expensify PR build.
Root Cause
Not fully pinned — stating this honestly:
Confirmed: no Expensify/App code change in 9.4.69-0 can produce this. The behaviour is decided by HybridAppModule.isHybridApp() and by the native closeReactNativeApp, and both the JS bridge and the App-side Android module are unchanged in this release.
Medium confidence: the regression came in with the Mobile-Expensify submodule bump f72dc07 → 3ac8c5c for this release. I could not read that diff (no access to the private repo), so I cannot confirm that PR Update version to 1.2.50-10 on staging #14097 specifically is at fault versus another commit in that range — a Mobile-Expensify engineer needs to confirm and revert there.
Secondary, pre-existing App-side sharp edge worth a separate fix (not a regression, present in production): the visibility gate uses the page's own isLoadingTryNewDot from useOnyx metadata (TroubleshootPage.tsx#L74) while the action uses a separate module-level isLoadingTryNewDot inside src/libs/actions/HybridApp/index.ts. When those two disagree, the item renders but closeReactNativeApp early-returns at HybridApp/index.ts#L113-L115 (shouldSetNVP && isLoadingTryNewDot, see TryNewDotUtils.ts#L24-L30) and the tap silently does nothing, with no feedback to the user. That matches the "tap and nothing happens" half of this report and is a plausible aggravating factor regardless of the native fix.
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/d57323dc99cbc181d0eb6d4ca00b5028da05cfb7004ae19bd4c7f96983af690a
melvin-bot commentedon Sep 3, 2026
Triggered auto assignment to @aldo-expensify (
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:
[-]Android-Switch to Expensify Classic navigates to mWeb OD instead of stays in app[/-][+]Android - Switch to Expensify Classic navigates to mWeb OD instead of stays in app[/+]MelvinBot commentedon Sep 3, 2026
🔍 Investigation Summary
Classification: Frontend bug (client-side — mobile/HybridApp native layer, not an App JS regression)
Causing PR: No
Expensify/AppPR in this release touches this code path. The only change inproduction...stagingthat can affect it is the Mobile-Expensify submodule bumpf72dc07→3ac8c5c(Medium confidence), which carries https://github.com/Expensify/Mobile-Expensify/pull/14097 — the same PR referenced in this bug report.Related Issues: #100246 (also Android-app-only, also staging-only, also filed against the same Mobile-Expensify PR build), #100228 (StagingDeployCash)
Recommendation: NEEDS INVESTIGATION
Every App-side file in the "Switch to Expensify Classic" path is byte-identical between
productionandstaging, so no App PR on this checklist can be reverted to fix this; the change has to be on the native/HybridApp side. Someone with Mobile-Expensify access needs to confirm whether the changes in that release (notably PR #14097) affect HybridApp native module registration / OldDot launch, and revert there if so.Assigned: no assignee change — the causing change appears to be in Mobile-Expensify and I do not have access to that repo, so I cannot identify the author or approving reviewers to assign. Please loop in the author of Mobile-Expensify#14097.
Labels: No changes.
DeployBlockerCashis kept — the App/Android deploy really is broken and the issue is not reproducible in production.DeployBlockerwas not present, so nothing was removed. Nothing here points at a backend/API fix.📋 Detailed Analysis
Verification
The full
production...stagingdiff for this release is 129 files. None of them is in the "Switch to Expensify Classic" path:src/pages/settings/Troubleshoot/TroubleshootPage.tsx— unchanged (last touched 2026-08-12, already in production)src/libs/actions/HybridApp/index.ts— unchanged (last functional change 2026-05-04)src/libs/TryNewDotUtils.ts— unchanged (last functional change 2026-06-29)src/libs/actions/Link.ts(openOldDotLink) — unchangedsrc/CONFIG.ts— unchangedmodules/hybrid-app/**(the JS↔native bridge, including the Android Kotlin module) — 0 files changed in this releasepackage.json— only theversionfield changed (9.4.66-0→9.4.69-0);@expensify/react-native-hybrid-appisfile:./modules/hybrid-appand was not bumpedandroid/app/build.gradle— onlyversionCode/versionNameI also checked the non-obvious candidates that could perturb Onyx loading state, since this flow is gated on it:
src/hooks/useOnyx.ts(rename-only refactor,originalUseOnyx→useOnyxWithoutSnapshots),src/setup/index.ts(removed one RAM-only key),src/libs/actions/Session/index.ts(2FAauthTokenparam),src/libs/Network/SequentialQueue.ts(offline comment/read-time handling). None of them touchNVP_TRY_NEW_DOT,CONFIG.IS_HYBRID_APP, or the redirect.The only remaining delta that reaches this behaviour is the submodule pointer:
Evidence
The menu item and both of its possible actions are here (permalinked at staging
c9dd46f6):TroubleshootPage.tsx#L125→shouldHideOldAppRedirect(tryNewDot, isLoadingTryNewDot, CONFIG.IS_HYBRID_APP, isDevelopment)TroubleshootPage.tsx#L133-L136→closeReactNativeApp({shouldSetNVP: true, isTrackingGPS})(stays in the native app)TroubleshootPage.tsx#L137-L143→switchToOldDot('')+openOldDotLink(CONST.OLDDOT_URLS.INBOX, true)(opens OldDot in the browser, i.e. mWeb)Which branch runs is decided purely by
src/CONFIG.ts#L143:…which is a straight pass-through to the native module (
modules/hybrid-app/src/index.native.ts#L6-L8). The implementation shipped in this repo for Android is the standalone stub that hard-codesfalse(ReactNativeHybridApp.kt#L12-L14), and itscloseReactNativeAppis a no-op log (L20-L22). The real implementation comes from the mobile build, so this JS behaves entirely according to what the native layer reports.That maps cleanly onto the two reported symptoms, and explains why they differ per device/build:
isHybridApp()resolving tofalseat runtime, so the standalone branch runs andopenOldDotLink(..., true)opens Classic in the browser (TroubleshootPage.tsx:141). This is also consistent with the item being visible in that state: withshouldRespectMobileLock === false, the visibility gate no longer hides the item whiletryNewDotis still loading (TryNewDotUtils.ts#L36-L42).HybridApp/index.ts#L103-L124), or the nativecloseReactNativeAppnot launching OldDot.Reproducibility supports a native-side cause: staging-only, production-unaffected, Android app only, while the App JS for this flow is identical to production. Two separate Android-only blockers on this checklist (this one and #100246, an app-shortcut/deep-link entry point) were both filed against the same Mobile-Expensify PR build.
Root Cause
Not fully pinned — stating this honestly:
Expensify/Appcode change in9.4.69-0can produce this. The behaviour is decided byHybridAppModule.isHybridApp()and by the nativecloseReactNativeApp, and both the JS bridge and the App-side Android module are unchanged in this release.f72dc07→3ac8c5cfor this release. I could not read that diff (no access to the private repo), so I cannot confirm that PR Update version to 1.2.50-10 on staging #14097 specifically is at fault versus another commit in that range — a Mobile-Expensify engineer needs to confirm and revert there.isLoadingTryNewDotfromuseOnyxmetadata (TroubleshootPage.tsx#L74) while the action uses a separate module-levelisLoadingTryNewDotinsidesrc/libs/actions/HybridApp/index.ts. When those two disagree, the item renders butcloseReactNativeAppearly-returns atHybridApp/index.ts#L113-L115(shouldSetNVP && isLoadingTryNewDot, seeTryNewDotUtils.ts#L24-L30) and the tap silently does nothing, with no feedback to the user. That matches the "tap and nothing happens" half of this report and is a plausible aggravating factor regardless of the native fix.view run
TaduJR commentedon Sep 3, 2026
Not able to repro this on latest main as well
Android-Native.mp4
Can you @AndrewGable
Thanks
war-in commentedon Sep 3, 2026
I think this investigation applies here too - #100246 (comment)Turned out to be related to https://github.com/Expensify/Mobile-Expensify/pull/14097
IuliiaHerets commentedon Sep 3, 2026
Issue is not reproducible in the latest build
screen-20260903-194432-1788453855502.mp4