Skip to content

[Due for payment 2025-04-02] [$250] Android Hybrid - Welcome to Expensify - A blank video screen display in the banner #58717

Closed

Description

@vincdargento

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: v9.1.15-0
Reproducible in staging?: Yes
Reproducible in production?: No
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: https://expensify.testrail.io/index.php?/cases/view/3155315
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: Pixel 7 Pro /Android 15
App Component: Left Hand Navigation (LHN)

Action Performed:

Precondition: OldDot Setup

  1. On the Web - Navigate to OldDot staging
  2. Login with a brand-new account
  3. Click on the 'Support' chat button to be redirected to ND
  4. Navigate back to the OldDot page
  5. Refresh OldDot
  6. Open console and run the following snippet: NVP.set('tryNewDot', {classicRedirect: {dismissed: true}});

Steps:

  1. Open the Hybrid app, sign in with the same account
  2. Tap on the hamburger button in the top left corner
  3. Tap on the 'Try New Expensify' button

Expected Result:

The video in the Welcome to Expensify plays normally

Actual Result:

After switching to ND, a blank screen is displayed in the Welcome to Expensify and the sound in the video is not heard on the phone's speaker.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6775571_1742392213845.blank_welcome.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021902456225860161379
  • Upwork Job ID: 1902456225860161379
  • Last Price Increase: 2025-03-19
  • Automatic offers:
    • suneox | Reviewer | 106621295
    • QichenZhu | Contributor | 106621297
    • ZhenjaHorbach | Contributor | 106621304
Issue OwnerCurrent Issue Owner: @MitchExpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    DeployBlockerCashThis issue or pull request should block deployment
    on Mar 19, 2025
  2. melvin-bot commented on Mar 19, 2025

    @melvin-bot

    Triggered auto assignment to @MitchExpensify (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.

  3. melvin-bot commented on Mar 19, 2025

    @melvin-bot

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

  4. melvin-bot commented on Mar 19, 2025

    @melvin-bot

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

  5. github-actions commented on Mar 19, 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.
  6. vincdargento commented on Mar 19, 2025

    @vincdargento
    Author

    @MitchExpensify 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. 49 remaining items

  8. melvin-bot commented on Mar 26, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.18-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2025-04-02. 🎊

    For reference, here are some details about the assignees on this issue:

  9. melvin-bot commented on Mar 26, 2025

    @melvin-bot

    @QichenZhu / @ZhenjaHorbach @MitchExpensify @QichenZhu / @ZhenjaHorbach The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  10. ZhenjaHorbach commented on Apr 1, 2025

    @ZhenjaHorbach
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      This is an our follow-up issue

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: NA

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    Regression Test Proposal

    Precondition: OldDot Setup

    • On the Web - Navigate to OldDot staging
    • Login with a brand-new account
    • Click on the 'Support' chat button to be redirected to ND
    • Navigate back to the OldDot page
    • Refresh OldDot
    • Open console and run the following snippet: NVP.set('tryNewDot', {classicRedirect: {dismissed: true}});

    Test steps:

    1. Open the Hybrid app, sign in with the same account
    2. Tap on the hamburger button in the top left corner
    3. Tap on the 'Try New Expensify' button
    4. Verify that the video in the Welcome to Expensify plays

    Do we agree 👍 or 👎

  11. melvin-bot commented on Apr 4, 2025

    @melvin-bot

    @MitchExpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

  12. MitchExpensify commented on Apr 6, 2025

    @MitchExpensify
    Contributor

    Payment summary:

  13. MitchExpensify commented on Apr 6, 2025

    @MitchExpensify
    Contributor

    @QichenZhu please accept the offer so I can issue payment: https://www.upwork.com/nx/wm/offer/106621297

    @ZhenjaHorbach please accept the offer so I can issue payment: https://www.upwork.com/nx/wm/offer/106621304

  14. MitchExpensify commented on Apr 8, 2025

    @MitchExpensify
    Contributor
  15. ZhenjaHorbach commented on Apr 8, 2025

    @ZhenjaHorbach
    Contributor

    Oh
    Sorry
    I didn't notice this issue 😅
    And I don't think we need payment here
    Since this is a follow up issue

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions