Skip to content

Android - The error message "Hmm... it's not here" appeared twice #40052

Closed

Description

@lanitochka17

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: 1.4.62-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): shussain+accoun1@applausemail.com
Issue reported by: Applause - Internal Team

Issue found when executing PR #39788

Action Performed:

  1. Open Expensify app
  2. Open that link "staging.new.expensify.com/a/asd" from other app (Whatsapp/Slack)
  3. Press back
  4. Verify LHN is shown instead of report screen

Expected Result:

Error should be displayed only once

Actual Result:

The error message "Hmm... it's not here" appeared twice

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6445043_1712779044815.WhatsApp_Video_2024-04-11_at_00.43.24.mp4

View all open jobs on GitHub

Activity

  1. melvin-bot commented on Apr 10, 2024

    @melvin-bot

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

  2. github-actions commented on Apr 10, 2024

    @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. lanitochka17 commented on Apr 10, 2024

    @lanitochka17
    Author

    @marcaaron 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

  4. lanitochka17 commented on Apr 10, 2024

    @lanitochka17
    Author

    We think that this bug might be related to #vip-vsp

  5. Julesssss commented on Apr 11, 2024

    @Julesssss
    Contributor

    Given that valid deep links work as expected, I'm demoting this from a blocker.

  6. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Apr 11, 2024
  7. melvin-bot commented on Apr 16, 2024

    @melvin-bot

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

  8. marcaaron commented on Apr 16, 2024

    @marcaaron
    Contributor

    I'm gonna close this as it is not really a "normal" action for a user to take and not worth prioritizing right now.

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions