-
Notifications
You must be signed in to change notification settings - Fork 89
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
chore: make pixel events more resilient #2856
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @anxolin , the app is not crashed in this PR!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @anxolin , it appears that the issue is also reproducible on Prod, so it can't be related to the upcoming release. |
I still address comments, I just want to consolidate the PRs. Pls @elena-zh let me know if it worked for you |
Summary
Pixels and any other analytics in the app should not break the user flow in case of an error.
This PR makes sure that if we have an error reporting Pixel (facebook, twitter, etc), we just log it and it doesn't propagate.
Additionally, this PR enables the pixel reporting for PRODUCTION and ENS (well, in the PR is enabled for testing purposes, but will be disabled before merging as stated in the code comment)
This PR tries to solve the issue reported by Elena:
To Test
@elena-zh can you check if this is fixing the issue?