Expensify / App

Welcome to New Expensify: a complete re-imagination of financial collaboration, centered around chat. Help us build the next generation of Expensify by sharing feedback and contributing to the code.
https://new.expensify.com
MIT License
3.54k stars 2.89k forks source link

The composer of the Chronos chat disappeared #49613

Closed m-natarajan closed 1 month ago

m-natarajan commented 1 month ago

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.39-0 Reproducible in staging?: Needs Reproduction Reproducible in production?: Needs Reproduction If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs: https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by: @quinthar Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1727029877973779

Action Performed:

  1. Go to staging.new.expensify.com
  2. Do some chats with Chronos and leave the laptop to sleep mode
  3. Access the site again

    Expected Result:

    No visual issues and all the chats reloaded

    Actual Result:

    The Chronos chat has a RBR, but don't see any error anywhere The composer of the Chronos chat disappeared

    Workaround:

    Unknown

    Platforms:

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

    • [ ] Android: Native
    • [ ] Android: mWeb Chrome
    • [ ] iOS: Native
    • [ ] iOS: mWeb Safari
    • [x] MacOS: Chrome / Safari
    • [ ] MacOS: Desktop

Screenshots/Videos

image (2)

image (3) reportID: 74050707 reportActionID: emailList: accountIDList: parentReportActionID: -1 clientLastReadTime: 2024-09-22 02:25:39.633 apiRequestType: write pusherSocketID: 777248.2686466 shouldRetry: true canCancel: true authToken: (redacted) referer: ecash platform: web api_setCookie: false email: dbarrett@expensify.com isFromDevEnv: false appversion: 9.0.39-0 clientUpdateID: 197270914

index.esm2017.js:539 Refused to connect to 'https://firebaseremoteconfig.googleapis.com/v1/projects/expensify-chat/namespaces/fireperf:fetch?key=AIzaSyDxzigVLZl4G8MP7jACQ0qpmADMzmrrON0' because it violates the following Content Security Policy directive: "connect-src 'self' https://*.pusher.com wss://.pusher.com https://.pusherapp.com https://secure.expensify.com/ https://staging-secure.expensify.com/ https://staging.expensify.com/ https://www.expensify.com/ https://accounts.google.com/gsi/ wss://sync.onfido.com/ https://telephony.onfido.com/ blob: .onfido.com wss://.onfido.com https://www.woopra.com/ https://sentry.io/ https://*.tiles.mapbox.com https://api.mapbox.com/ https://*.googleusercontent.com https://*.smartlook.cloud https://events.mapbox.com/ https://edge.fullstory.com/ https://rs.fullstory.com/ https://firebaseinstallations.googleapis.com/ data:".

(anonymous) @ index.esm2017.js:539 Promise.then (anonymous) @ index.esm2017.js:522 (anonymous) @ index.esm2017.js:482 (anonymous) @ index.esm2017.js:649 Show 4 more frames Show lessUnderstand this error index.esm2017.js:539 Refused to connect to 'https://firebaseremoteconfig.googleapis.com/v1/projects/expensify-chat/namespaces/fireperf:fetch?key=AIzaSyDxzigVLZl4G8MP7jACQ0qpmADMzmrrON0' because it violates the document's Content Security Policy.

Add any screenshot/video evidence

View all open jobs on GitHub

melvin-bot[bot] commented 1 month ago

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

MelvinBot commented 1 month ago

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

slafortune commented 1 month ago

I wasn't able to recreate this -

image
slafortune commented 1 month ago

Closing for now - not reproducible.