You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-04-02] [$250] Android Hybrid - Welcome to Expensify - A blank video screen display in the banner #58717
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
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}});
Steps:
Open the Hybrid app, sign in with the same account
Tap on the hamburger button in the top left corner
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.
👋 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:
Identify the pull request that introduced this issue and revert it.
@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.
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:
@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]
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:
Open the Hybrid app, sign in with the same account
Tap on the hamburger button in the top left corner
Tap on the 'Try New Expensify' button
Verify that the video in the Welcome to Expensify plays
Activity
melvin-bot commentedon Mar 19, 2025
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.melvin-bot commentedon Mar 19, 2025
Triggered auto assignment to @mjasikowski (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Mar 19, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Mar 19, 2025
👋 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:
vincdargento commentedon Mar 19, 2025
@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.
49 remaining items
melvin-bot commentedon Mar 26, 2025
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:
melvin-bot commentedon Mar 26, 2025
@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]
ZhenjaHorbach commentedon Apr 1, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[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
Test steps:
Do we agree 👍 or 👎
melvin-bot commentedon Apr 4, 2025
@MitchExpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!
MitchExpensify commentedon Apr 6, 2025
Payment summary:
$250 @ZhenjaHorbach requires payment automatic offer (Contributor)
MitchExpensify commentedon Apr 6, 2025
@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
MitchExpensify commentedon Apr 8, 2025
Bump @QichenZhu @ZhenjaHorbach
ZhenjaHorbach commentedon Apr 8, 2025
Oh
Sorry
I didn't notice this issue 😅
And I don't think we need payment here
Since this is a follow up issue