[HOLD for payment 2024-12-11] [HOLD for payment 2024-12-09] iOS/Android - Track expense & Log in - Background turns blank when educational modal comes up

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.69-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team

Action Performed:

Issue 1:

Precondition:

• Use an account that has "Track expense" instead of "Create expense".

1. Launch ND or hybrid app.
2. Open FAB.
3. Open Track expense.

Issue 2:

1. Create a new account on Old Dot.
2. Log in to the same account for the first time on hybrid app.
3. App will auto redirect to ND on hybrid app.

Expected Result:

Background will not turn blank when educational modal comes up.

Actual Result:

Background turns blank when educational modal comes up.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6680793_1732987997742.track_expense_video_modal.mp4

Bug6680793_1732987997761.new_user_video_modal.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @abekkala

[melvin-bot]

Triggered auto assignment to @abekkala (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]

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

[melvin-bot]

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

[github-actions]

👋 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.

[mountiny]

This one does not seem to be a blocker to me but we should fix it for sure

@kirillzyusko @hannojg @chrispader

[adamgrzybowski]

@mountiny I will take a look at this one

[shubham1206agra]

@adamgrzybowski Let me know when you are ready for review. I can start doing the review.

[adamgrzybowski]

@shubham1206agra You can start. I am currently recording videos and got a little stuck on building android 😄

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

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

• [CP Staging] Fix transparency for basic modal navigators #53381

If no regressions arise, payment will be issued on 2024-12-09. 🎊

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

• @adamgrzybowski does not require payment (Contractor)

[melvin-bot]

@mountiny @abekkala @adamgrzybowski 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]

[mountiny]

@shubham1206agra can you please complete the checklist? Thanks!

[melvin-bot]

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

• [CP Staging] Fix transparency for basic modal navigators #53381

If no regressions arise, payment will be issued on 2024-12-11. 🎊

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

• @shubham1206agra requires payment (Needs manual offer from BZ)
• @adamgrzybowski does not require payment (Contractor)

[melvin-bot]

@shubham1206agra @abekkala @shubham1206agra 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]

[melvin-bot]

Payment Summary

Upwork Job

• ROLE: @shubham1206agra paid $(AMOUNT) via Upwork (LINK)
• Contributor: @adamgrzybowski is from an agency-contributor and not due payment

BugZero Checklist (@abekkala)

• I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
• I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
• I have paid out the Upwork contracts or cancelled the ones that are incorrect
• I have verified the payment summary above is correct

[abekkala]

@shubham1206agra can you please complete the checklist? Thanks!

[abekkala]

PAYMENT SUMMARY FOR DEC 11

• Fix: @adamgrzybowski - no payment needed
• PR Review: @shubham1206agra [$250] Offer
  payment made once checklist is completed

[abekkala]

@shubham1206agra friendly bump here for checklist - once completed I can issue payment

[shubham1206agra]

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.

  Link to comment: https://github.com/Expensify/App/pull/49937/files#r1884148854

• [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: Not Required

• [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.

• [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

  Link to issue:

Regression Test Proposal

Test:

No tests required as this issue was a deploy blocker and tests is already in TestRail.

Do we agree 👍 or 👎

[melvin-bot]

@abekkala, @mountiny, @shubham1206agra, @adamgrzybowski Whoops! This issue is 2 days overdue. Let's get this updated quick!

[shubham1206agra]

@abekkala Can you please pay here?

[abekkala]

@shubham1206agra yes - I did post summary on day of payment due (dec 11) but checklist was not completed until Dec 13.
You'll want to make sure that you're posting the checklist items before or on day of payment due.

[abekkala]

@shubham1206agra payment sent and contract ended - thank you! 🎉