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 - Native share - Share flow does not open, "Please sign in" message is shown #100258
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):jsdoijnodsdisojo@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Samsung Galaxy S25 FE / Android 16 App Component: Other
Action Performed:
Precondition:
User is logged in.
Kill the app.
Share an image from device gallery to Expensify app.
Expected Result:
Share flow will open.
Actual Result:
Home tab opens.
"Please sign in before sharing a file with Expensify" is shown when user is logged in.
👋 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 (mobile app / native layer — not a backend/API bug) Causing PR: https://github.com/Expensify/Mobile-Expensify/pull/14097 — the only native mobile change in 9.4.69-0 (Medium confidence — see caveat below) Related Issues: #100246, #100256, #100257 (same release, Android app only, staging only, and 2 of the 3 were also filed against the same PR)
Recommendation: REVERT
Revert the Mobile-Expensify PR included in this release (i.e. roll the submodule pointer back to the 9.4.68-1 native build) — it is the only change in 9.4.69-0 that touches native Android, and four Android-native-only regressions in this release all cluster on Android intent / deep-link / session-handoff behavior. No Expensify/App PR in this checklist can produce this symptom.
Assigned: none — I could not resolve the author/approving reviewers of the causing PR from this environment (that repo is not readable here). Could whoever shipped https://github.com/Expensify/Mobile-Expensify/pull/14097 please confirm and self-assign? Labels: No changes. DeployBlockerCash is correct and stays (this blocks the mobile app deploy). DeployBlocker was not applied, and nothing warrants adding it — this is not a backend/API failure.
📋 Detailed Analysis
Evidence
Staging only, not production, and Android app only, on 9.4.69-0. So the cause is in this release.
The failing message is not in Expensify/App at all. I grepped the whole App checkout — src/, android/, node_modules/, patches/ — for "before sharing a file" / "sign in before sharing" and there are zero matches. The copy Please sign in before sharing a file with Expensify was agreed in [Native Share] Clean Up - Wrong error message when trying to share while we are logged out. #58748 and, per that thread, implemented on the native/hybrid side, not in NewDot. So the check that decides "user is not signed in" and blocks the share intent runs in the hybrid native layer, not in App JS.
No App PR in this deploy can cause it. I pulled the changed-file list for all 21 App PRs on the checklist (Deploy Checklist: New Expensify 2026-09-02 #100228). Only two touch anything adjacent, and both are ruled out:
[No QA] Pass authtoken back through SignInUser #100084 (src/libs/actions/Session/index.ts) is strictly additive on the 2FA branch — authToken is only attached when twoFactorAuthCode && storedAuthToken. It cannot affect an already-signed-in user's cold start.
No App PR in this release touches android/, HybridApp, navigation linking config, or share-intent code.
The only remaining change is the native one. The checklist records exactly one Mobile-Expensify PR for this release — the submodule bump to cb8902a → https://github.com/Expensify/Mobile-Expensify/pull/14097 — plus the subsequent version bumps through 9.4.69-0.
Sibling blockers corroborate. All four Android-app-only, staging-only blockers in this release are intent / deep-link / hybrid-handoff failures:
this issue — cold-start share intent is rejected as "not signed in"
src/pages/Share/ShareRootPage.tsx#L101-L177 — this only runs once navigation has already landed on share/root. In this bug the Home tab opens instead, so the failure happens strictly before any App JS share code executes.
Note the standalone-vs-hybrid distinction: the shipped Android binary is the hybrid app, so the launcher/intent entry point that runs first is the native one, and that is where the sign-in gate lives.
Root Cause
On a cold start the share intent is received natively before the NewDot JS session is available. The native layer evaluates whether a session exists, decides the user is signed out, drops the share payload, shows Please sign in before sharing a file with Expensify, and falls through to the Home tab instead of routing to share/root. Something in this release changed that native cold-start intent/session handoff so an already-signed-in user is now seen as signed out — the same class of failure that also breaks the Classic handoff (#100256), magic-link deep links (#100257), and app shortcuts (#100246).
Confidence caveat (stated honestly): I could not read the diff of the causing PR — the Mobile-Expensify repository is not accessible from this environment (gh returns 404 and clone/ls-remote return 403), so I could not confirm line-by-line which native change introduced it, and I could not resolve its author or approving reviewers. Attribution therefore rests on elimination (no App PR can cause it), on the fact that it is the only native change in the release, and on the four-blocker Android-only cluster. That is why this is Medium, not High, confidence. Someone with access to that repo should confirm against the diff before or alongside the revert — but given four deploy blockers point at the same native change, reverting first is the right call.
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/a08bc628b80daf677ec466a520c338f3c1f68d03ca4a807b29def47eb783e0be
melvin-bot commentedon Sep 3, 2026
Triggered auto assignment to @Valforte (
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 (mobile app / native layer — not a backend/API bug)
Causing PR: https://github.com/Expensify/Mobile-Expensify/pull/14097 — the only native mobile change in
9.4.69-0(Medium confidence — see caveat below)Related Issues: #100246, #100256, #100257 (same release, Android app only, staging only, and 2 of the 3 were also filed against the same PR)
Recommendation: REVERT
Revert the Mobile-Expensify PR included in this release (i.e. roll the submodule pointer back to the
9.4.68-1native build) — it is the only change in9.4.69-0that touches native Android, and four Android-native-only regressions in this release all cluster on Android intent / deep-link / session-handoff behavior. NoExpensify/AppPR in this checklist can produce this symptom.Assigned: none — I could not resolve the author/approving reviewers of the causing PR from this environment (that repo is not readable here). Could whoever shipped https://github.com/Expensify/Mobile-Expensify/pull/14097 please confirm and self-assign?
Labels: No changes.
DeployBlockerCashis correct and stays (this blocks the mobile app deploy).DeployBlockerwas not applied, and nothing warrants adding it — this is not a backend/API failure.📋 Detailed Analysis
Evidence
Staging only, not production, and Android app only, on
9.4.69-0. So the cause is in this release.The failing message is not in
Expensify/Appat all. I grepped the whole App checkout —src/,android/,node_modules/,patches/— for"before sharing a file"/"sign in before sharing"and there are zero matches. The copyPlease sign in before sharing a file with Expensifywas agreed in [Native Share] Clean Up - Wrong error message when trying to share while we are logged out. #58748 and, per that thread, implemented on the native/hybrid side, not in NewDot. So the check that decides "user is not signed in" and blocks the share intent runs in the hybrid native layer, not in App JS.No App PR in this deploy can cause it. I pulled the changed-file list for all 21 App PRs on the checklist (Deploy Checklist: New Expensify 2026-09-02 #100228). Only two touch anything adjacent, and both are ruled out:
src/libs/actions/Session/index.ts) is strictly additive on the 2FA branch —authTokenis only attached whentwoFactorAuthCode && storedAuthToken. It cannot affect an already-signed-in user's cold start.src/pages/Share/ShareDetailsPage.tsx, but only to thread onboarding status intoopenReport. That page is downstream of the share flow; here the share flow never opens at all.android/, HybridApp, navigation linking config, or share-intent code.The only remaining change is the native one. The checklist records exactly one Mobile-Expensify PR for this release — the submodule bump to
cb8902a→ https://github.com/Expensify/Mobile-Expensify/pull/14097 — plus the subsequent version bumps through9.4.69-0.Sibling blockers corroborate. All four Android-app-only, staging-only blockers in this release are intent / deep-link / hybrid-handoff failures:
Expense-User not directed to scan receipt flow when opening via app short cut. #100246, Android - Switch to Expensify Classic navigates to mWeb OD instead of stays in app #100256 and this issue each cite https://github.com/Expensify/Mobile-Expensify/pull/14097 in the report, and Android - Switch to Expensify Classic navigates to mWeb OD instead of stays in app #100256 is explicitly
Bug source: Pull Request QA execution. One shared native root cause explains all four far better than four unrelated JS PRs.Verification
Affected code path, App side (all confirmed unable to produce the symptom):
android/app/src/main/java/com/expensify/chat/MainActivity.kt#L63-L86— App's intent handling just dispatches throughIntentHandlerFactory; there is no session/sign-in check anywhere in it.android/app/src/main/java/com/expensify/chat/ShareActionHandlerModule.kt#L23-L32—processFilesonly reads the already-persisted shared file out of SharedPreferences; its only failure mode is"No data found", not a sign-in prompt.src/pages/Share/ShareRootPage.tsx#L101-L177— this only runs once navigation has already landed onshare/root. In this bug the Home tab opens instead, so the failure happens strictly before any App JS share code executes.Note the standalone-vs-hybrid distinction: the shipped Android binary is the hybrid app, so the launcher/intent entry point that runs first is the native one, and that is where the sign-in gate lives.
Root Cause
On a cold start the share intent is received natively before the NewDot JS session is available. The native layer evaluates whether a session exists, decides the user is signed out, drops the share payload, shows
Please sign in before sharing a file with Expensify, and falls through to the Home tab instead of routing toshare/root. Something in this release changed that native cold-start intent/session handoff so an already-signed-in user is now seen as signed out — the same class of failure that also breaks the Classic handoff (#100256), magic-link deep links (#100257), and app shortcuts (#100246).Confidence caveat (stated honestly): I could not read the diff of the causing PR — the Mobile-Expensify repository is not accessible from this environment (
ghreturns 404 and clone/ls-remote return 403), so I could not confirm line-by-line which native change introduced it, and I could not resolve its author or approving reviewers. Attribution therefore rests on elimination (no App PR can cause it), on the fact that it is the only native change in the release, and on the four-blocker Android-only cluster. That is why this is Medium, not High, confidence. Someone with access to that repo should confirm against the diff before or alongside the revert — but given four deploy blockers point at the same native change, reverting first is the right call.view run
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_Recording_20260904_003034_Expensify.mp4
melvin-bot commentedon Sep 3, 2026
@Valforte — to hire @TaduJR on Upwork, add the External label so a job is created and the offer is sent automatically.
Valforte commentedon Sep 3, 2026
Adding @TaduJR so you can keep an eye on it when pushing the R8 PR again
melvin-bot commentedon Sep 8, 2026
@TaduJR Eep! 4 days overdue now. Issues have feelings too...
melvin-bot commentedon Sep 10, 2026
@TaduJR Still overdue 6 days?! Let's take care of this!
TaduJR commentedon Sep 12, 2026
Not overdue
We can close this @Valforte
Resolved by https://github.com/Expensify/Mobile-Expensify/pull/14104