Skip to content

Test Drive - Test Drive demo site shows "This content is blocked" #66121

Closed

Description

@mitarachim

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.81-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #65900
Email or phone of affected tester (no customers): dawitexpensify+davccb@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 14.5/ Chrome
App Component: Other

Action Performed:

Prerequisite: Invite a brand new account to a workspace

  1. Sign-in with the invited user.
  2. Click on the + FAB.
  3. Click the "Take a 2-minute test drive" option.

Expected Result:

the Test Drive demo is shown with this content: https://expensify.navattic.com/35609gb.

Actual Result:

Broken site. This content is blocked

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6888160_1752559181405.Screen_Recording_2025-07-15_at_8.39.36_in_the_morning.mp4

View all open jobs on GitHub

Activity

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

    @melvin-bot

    Triggered auto assignment to @RachCHopkins (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. github-actions commented on Jul 15, 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.
  4. melvin-bot commented on Jul 15, 2025

    @melvin-bot

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

  5. melvin-bot commented on Jul 15, 2025

    @melvin-bot

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

  6. 1 remaining item

  7. MariaHCD commented on Jul 15, 2025

    @MariaHCD
    Contributor

    This doesn't need to block the API deploy

  8. fabioh8010 commented on Jul 15, 2025

    @fabioh8010
    Contributor

    @MariaHCD Do you think we can involve someone internally to take a look at this? I'm assuming this issue is on BE or some internal configuration because I don't see such configs on FE.

  9. melvin-bot commented on Jul 15, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  10. MariaHCD commented on Jul 16, 2025

    @MariaHCD
    Contributor

    @fabioh8010 Yes, I believe we need to add expensify.navattic.com to our CSP rules. I'll see if I can spin up a PR for this.

  11. MariaHCD commented on Jul 16, 2025

    @MariaHCD
    Contributor
  12. MariaHCD commented on Jul 16, 2025

    @MariaHCD
    Contributor

    Internal PR was merged: https://github.com/Expensify/Cloudflare-Workers/pull/198

    Tested on staging:

    Image

    Going to deploy to production so this won't happen on production

  13. MariaHCD commented on Jul 16, 2025

    @MariaHCD
    Contributor

    This should now be resolved and doesn't need to block the App deploy.

    @mitarachim when you have a chance, can you retest on staging?

  14. luacmartins commented on Jul 16, 2025

    @luacmartins
    Contributor

    This is fixed in staging

    Image
  15. luacmartins commented on Jul 16, 2025

    @luacmartins
    Contributor

    I just noticed that the background view of the App is quite outdated. Do we have plans to fix that somewhere?

  16. MariaHCD commented on Jul 17, 2025

    @MariaHCD
    Contributor

    I just noticed that the background view of the App is quite outdated. Do we have plans to fix that somewhere?

    Looks like we're moving to Storylane: #65382

    So I believe those will have the most up-to-date UI

    cc: @danielrvidal @marcaaron

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions