Skip to content

Android - Native share - Share flow does not open, "Please sign in" message is shown #100258

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: 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.
  1. 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.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7249726_1788414200729.Screen_Recording_20260903_134017_Expensify.mp4

View all open jobs on GitHub

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

Issue OwnerCurrent Issue Owner: @TaduJR
Issue OwnerCurrent Issue Owner: @TaduJR

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/a08bc628b80daf677ec466a520c338f3c1f68d03ca4a807b29def47eb783e0be

  2. added
    DeployBlockerCashThis issue or pull request should block deployment
    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 @Valforte (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 (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

    Verification

    Affected code path, App side (all confirmed unable to produce the symptom):

    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.


    view run

  7. war-in commented on Sep 3, 2026

    @war-in
    Contributor

    I think this investigation applies here too - #100246 (comment)

    Turned out to be related to https://github.com/Expensify/Mobile-Expensify/pull/14097

  8. IuliiaHerets commented on Sep 3, 2026

    @IuliiaHerets

    Issue is not reproducible in the latest build

    Screen_Recording_20260904_003034_Expensify.mp4
  9. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Sep 3, 2026
  10. melvin-bot commented on Sep 3, 2026

    @melvin-bot

    @Valforte — to hire @TaduJR on Upwork, add the External label so a job is created and the offer is sent automatically.

  11. Valforte commented on Sep 3, 2026

    @Valforte
    Contributor

    Adding @TaduJR so you can keep an eye on it when pushing the R8 PR again

  12. melvin-bot commented on Sep 8, 2026

    @melvin-bot

    @TaduJR Eep! 4 days overdue now. Issues have feelings too...

  13. melvin-bot commented on Sep 10, 2026

    @melvin-bot

    @TaduJR Still overdue 6 days?! Let's take care of this!

  14. TaduJR commented on Sep 12, 2026

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

Metadata

Metadata

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