[HOLD for payment 2024-06-06] [HOLD for payment 2024-05-03] [HOLD for payment 2024-05-02] Web - "Error: FullStory is not loaded" console error shows up

@laurenreidexpensify

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.65-0
Reproducible in staging?: Y
Reproducible in production?: N
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

Go to staging.new.expensify.com
Log in.

Expected Result:

No console error will show up.

Actual Result:

"Error: FullStory is not loaded" console error shows up.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6459941_1713948779812!Screenshot_2024-04-24_at_09 53 30

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @laurenreidexpensify

@laurenreidexpensify

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

@nkuoch

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

👋 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.
Find someone who can quickly fix the issue.
Fix the issue yourself.

@laurenreidexpensify

@laurenreidexpensify 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.

We think this issue might be related to the #vip-vsb.

Production

Recording.2398.mp4

Regression from this one:
#40294

Seems this one should be:

App/src/libs/fullstory/index.ts

Lines 31 to 33 in c9cf767

    
           if (isInitialized()) { 
        
               init({orgId: ''}, resolve); 
        
           } else {

 if (!isInitialized()) { 
     init({orgId: ''}, resolve); 
 }

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

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

[CP Staging] Changing properties being used by Fullstory #40807

If no regressions arise, payment will be issued on 2024-05-02. 🎊

@danieldoglas

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:

[@danieldoglas] The PR that introduced the bug has been identified. Link to the PR:
[@danieldoglas] 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:
[@danieldoglas] 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:
[@danieldoglas] Determine if we should create a regression test for this bug.
[@danieldoglas] 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.
[@laurenreidexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

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

[CP Staging] Changing properties being used by Fullstory #40807

If no regressions arise, payment will be issued on 2024-05-03. 🎊

@danieldoglas

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:

[@danieldoglas] The PR that introduced the bug has been identified. Link to the PR:
[@danieldoglas] 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:
[@danieldoglas] 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:
[@danieldoglas] Determine if we should create a regression test for this bug.
[@danieldoglas] 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.
[@laurenreidexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Closing this since error doesn't exist anymore

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

[CP Staging] Changing properties being used by Fullstory #40807

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

@danieldoglas

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:

[@danieldoglas] The PR that introduced the bug has been identified. Link to the PR:
[@danieldoglas] 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:
[@danieldoglas] 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:
[@danieldoglas] Determine if we should create a regression test for this bug.
[@danieldoglas] 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.
[@laurenreidexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Navigation Menu

Repository navigation

[HOLD for payment 2024-06-06] [HOLD for payment 2024-05-03] [HOLD for payment 2024-05-02] Web - "Error: FullStory is not loaded" console error shows up #40860

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

11 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[HOLD for payment 2024-06-06] [HOLD for payment 2024-05-03] [HOLD for payment 2024-05-02] Web - "Error: FullStory is not loaded" console error shows up #40860

Description

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

Activity

melvin-bot commented on Apr 24, 2024

melvin-bot commented on Apr 24, 2024

github-actions commented on Apr 24, 2024

izarutskaya commented on Apr 24, 2024

izarutskaya commented on Apr 24, 2024

izarutskaya commented on Apr 24, 2024

hungvu193 commented on Apr 24, 2024

11 remaining items

melvin-bot commented on Apr 25, 2024

melvin-bot commented on Apr 25, 2024

melvin-bot commented on Apr 25, 2024

melvin-bot commented on Apr 26, 2024

melvin-bot commented on Apr 26, 2024

danieldoglas commented on Apr 28, 2024

melvin-bot commented on May 30, 2024

melvin-bot commented on May 30, 2024

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions