-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to sign in on staging #10917
Comments
Triggered auto assignment to @cdraeger11 ( |
Looks like the errors from this CSP rule here: https://github.com/Expensify/Cloudflare-Workers/blob/26d94b8fc324d03c8817b6860726c0ebc41770be/new.expensify.com/wrangler.toml |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Thanks for the ping, I will create a revert PR. Not sure if we can fix this fast |
Ah, where is that defined 🤔 |
Yeah, let's revert these changes and then make a PR to update CSP rules and then we can re-do these changes |
Tested logging in staging after the revert and worked good. |
Am I eligible for reporting bonus here? Thanks. |
Triggered auto assignment to @kevinksullivan ( |
@kevinksullivan Would you be able to pay out @mdneyazahmad for reporting this bug. Thank you! |
I can tackle this! |
Current assignee @dylanexpensify is eligible for the External assigner, not assigning anyone new. |
@mdneyazahmad ^ 😄 |
@dylanexpensify It shows "Job not found." Thank you! |
https://www.upwork.com/jobs/~01f0713bffe19757ca huh - try this link? Or send me your name and I'll invite you to the job! |
I applied |
Offer sent! |
@dylanexpensify I have accepted the offer. Thank you! |
payment sent, contract ended, job closed! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
User should be able to log in
Actual Result:
Describe what actually happened

Infinite spinner
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
No
Platform:
Where is this issue occurring?
Version Number:
Reproducible in staging?:
Reproducible in production?:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @mdneyazahmad
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1662709037179189
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: