Skip to content

Emails-Invited to the WS member is not signed in after tapping Get started in the email #95878

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number: 95814
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://test-management.browserstack.com/projects/2219752/folder/13176726/test-cases/41237087
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: iPhone 15 iOS 26.5
App Component: Notifications

Action Performed:

Preconditions: User A on the secondary device created a workspace and invited a non-existing account (User B) as a member

  1. As User B, fresh install the app
  2. Open the app, enable staging
  3. Background the app (do not "kill")
  4. Open Gmail app, open "User A invited you to the User A's workspace" email
  5. Tap "Get started" green button

Expected Result:

Invited to the WS member is signed in after tapping Get started in the email

Actual Result:

Invited to the WS member is not signed in after tapping Get started in the email

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7205195_1783726304311.not_signed_in.mp4

View all open jobs on GitHub

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

Activity

  1. applause-bot commented on Jul 11, 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/0ed68f9f5cf8cb89c8843936274b6d07ec20f971f615de31e56181e02793e674

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

    @melvin-bot

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

  4. melvin-bot commented on Jul 11, 2026

    @melvin-bot

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

  5. github-actions commented on Jul 11, 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 Jul 11, 2026

    @MelvinBot
    Contributor

    ⚠️ Something went wrong. This may be a transient issue — try again. If it persists, check status.anthropic.com.

    Run details

  7. rlinoz commented on Jul 13, 2026

    @rlinoz
    Contributor

    hmm maybe it is related to #92482, let me check.

  8. rlinoz commented on Jul 13, 2026

    @rlinoz
    Contributor
  9. m-natarajan commented on Jul 13, 2026

    @m-natarajan

    Unable to reproduce, iPhone13/26.5, v9.3.33-2

    retest1.mp4
  10. removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Jul 13, 2026
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.EngineeringHourlyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions