Skip to content

Android - Onboarding - No error message for wrong magic code on private domain #60823

Closed

Description

@nlemma

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: 9.1.32-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check - no OTP prompt on prod
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only
If this was caught during regression testing, add the test name, ID and link from TestRail: #54912
Email or phone of affected tester (no customers): akabskoshis@agiuse.com
Issue reported by: Applause Internal Team
Device used: Samsung Galaxy Z Fold 4 / Android 14
App Component: Other

Action Performed:

  1. Launch Expensify app.
  2. Log in with this private domain email - @agiuse.com
  3. Enter name > Continue.
  4. On magic code page, enter any code (any code will be the incorrect code).

Expected Result:

There will be a message saying "Invalid code".

Actual Result:

There is an error but it is missing message.

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6811656_1745499005509.Screen_Recording_20250424_204751_Expensify.mp4

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerCashThis issue or pull request should block deployment
    on Apr 24, 2025
  2. github-actions commented on Apr 24, 2025

    @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.
  3. melvin-bot commented on Apr 24, 2025

    @melvin-bot

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

  4. melvin-bot commented on Apr 24, 2025

    @melvin-bot

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

  5. melvin-bot commented on Apr 24, 2025

    @melvin-bot

    Triggered auto assignment to @trjExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  6. nlemma commented on Apr 24, 2025

    @nlemma
    Author

    @trjExpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

  7. 5 remaining items

  8. blimpich commented on Apr 24, 2025

    @blimpich
    Contributor

    Discussing here: https://expensify.slack.com/archives/C01GTK53T8Q/p1745512280269079

    Personally I'd say this is on the edge of being a deploy blocker for me, because it (A) only happens on Android and (B) only happens when they put the wrong code in and (C) still shows UI indicating an error, just no text, and (D) doesn't prevent them from continuing in the onboarding flow.

  9. melvin-bot commented on Apr 24, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  10. melvin-bot commented on Apr 24, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  11. blimpich commented on Apr 24, 2025

    @blimpich
    Contributor

    We have a fix in the works here: #60856

  12. blimpich commented on Apr 24, 2025

    @blimpich
    Contributor

    Hmm, weird, I didn't close this, and it should be kept open. We're still QA-ing. Weird automation mishap.

  13. blimpich commented on Apr 25, 2025

    @blimpich
    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.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions