Skip to content

[HOLD for payment 2024-10-17] [$250] Book travel - Book travel animation becomes blank while RHP is dismissed #49744

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: 9.0.40-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): applausetester+kh230901@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Open FAB
  3. Click Book travel
  4. Dismiss the RHP

Expected Result:

Book travel animation will not become blank while RHP is dismissed

Actual Result:

Book travel animation becomes blank while RHP is dismissed

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

Bug6615160_1727291080522.20240926_020845.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021840763606281462254
  • Upwork Job ID: 1840763606281462254
  • Last Price Increase: 2024-09-30
  • Automatic offers:
    • suneox | Reviewer | 104245520
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @sakluger

Activity

  1. melvin-bot commented on Sep 25, 2024

    @melvin-bot

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

  2. github-actions commented on Sep 25, 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. rushatgabhane commented on Sep 25, 2024

    @rushatgabhane
    Member

    don't know what caused it, but def NOT A BLOCKER

  4. Nodebrute commented on Sep 25, 2024

    @Nodebrute
    Contributor

    This happens with all the animations, like on the wallet, security, and troubleshoot pages.

  5. rushatgabhane commented on Sep 25, 2024

    @rushatgabhane
    Member

    let's close 😄

  6. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Sep 25, 2024
  7. MonilBhavsar commented on Sep 25, 2024

    @MonilBhavsar
    Contributor

    Thanks for looking! Demoting from blocker, but let's try if we can fix it

  8. neonbhai commented on Sep 25, 2024

    @neonbhai
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    Default name in name field displays user/report ID instead of user/report name

    What is the root cause of that problem?

    This happens as we render an empty view here if the user has navigated away. The issue we set hasNavigatedAway quickly before the RHP animation has been completed. This then shows the user an empty view while RHP is dismissing.

    What changes do you think we should make in order to solve the problem?

    We will change the state change here: to run after interactions, which will make it wait for the animation to be completed:

    // If the page navigates to another screen, the image fails to load, app is in background state, animation file isn't ready, or the splash screen isn't hidden yet,
    // we'll just render an empty view as the fallback to prevent
    // 1. memory leak, see issue: https://github.com/Expensify/App/issues/36645
    // 2. heavy rendering, see issues: https://github.com/Expensify/App/issues/34696 and https://github.com/Expensify/App/issues/47273
    // 3. lag on react navigation transitions, see issue: https://github.com/Expensify/App/issues/44812
    if (
    hasNavigatedAway ||

    InteractionManager.runAfterInteractions(() => {
        setHasNavigatedAway(true);
    });

    Result

    Screen.Recording.2024-09-26.at.2.36.22.AM.mov
  9. rushatgabhane commented on Sep 25, 2024

    @rushatgabhane
    Member

    @MonilBhavsar @neonbhai the reasons mentioned here suggest that we should do nothing. Or it may cause issues 1, 2, 3

    But I guess that is only the case when the image hasn't loaded

    // If the page navigates to another screen, the image fails to load, app is in background state, animation file isn't ready, or the splash screen isn't hidden yet,
    // we'll just render an empty view as the fallback to prevent
    // 1. memory leak, see issue: https://github.com/Expensify/App/issues/36645
    // 2. heavy rendering, see issues: https://github.com/Expensify/App/issues/34696 and https://github.com/Expensify/App/issues/47273
    // 3. lag on react navigation transitions, see issue: https://github.com/Expensify/App/issues/44812
    if (
    hasNavigatedAway ||

  10. 47 remaining items

  11. melvin-bot commented on Oct 10, 2024

    @melvin-bot

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

  12. melvin-bot commented on Oct 10, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.47-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 2024-10-17. 🎊

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

  13. melvin-bot commented on Oct 10, 2024

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@suneox] The PR that introduced the bug has been identified. Link to the PR:
    • [@suneox] 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:
    • [@suneox] A discussion in #expensify-bugs 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:
    • [@suneox] Determine if we should create a regression test for this bug.
    • [@suneox] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [@sakluger] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  14. sakluger commented on Oct 17, 2024

    @sakluger
    Contributor

    Summarizing payment on this issue:

    Contributor: @layacat $250, please apply to the Upwork job or comment with your Upwork profile
    Contributor+: @suneox $250, paid via Upwork

    @suneox please complete the BZ checklist.

  15. layacat commented on Oct 18, 2024

    @layacat
    Contributor

    Hi @sakluger I submitted work on Upwork, please check

  16. suneox commented on Oct 18, 2024

    @suneox
    Contributor

    Checklist

    • [@suneox] The PR that introduced the bug has been identified. Link to the PR: Prevent Lottie from running in the background after navigating to other pages #47960
    • [@suneox] 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
    • [@suneox] A discussion in #expensify-bugs 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: N/A
    • [@suneox] Determine if we should create a regression test for this bug: N/A
    • [@suneox] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again. N/A
  17. sakluger commented on Oct 18, 2024

    @sakluger
    Contributor

    @layacat thanks! I didn't realize you had already applied. I sent an offer via Upwork.

  18. layacat commented on Oct 21, 2024

    @layacat
    Contributor

    I just submitted work for payment on Upwork. Please check

  19. sakluger commented on Oct 21, 2024

    @sakluger
    Contributor

    Perfect, thanks! All contracts have been paid out now.

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