-
Notifications
You must be signed in to change notification settings - Fork 28
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
Bug: posthog.on('error') always catches http fetch error #180
Comments
Also i've noticed that the fetch error is:
|
Hi @sirpy thanks for reporting this, let me check it. |
@sirpy or @L03TJ3 can you enable Do first thing after the SDK is init: I cannot reproduce it locally so I'm not sure what it can be. |
@marandaneto |
It's not really because of |
If you init the SDK with |
Bug description
We added a logger to catch whenever posthog failed to load at all. It seems posthog.on('error') should be used for this.
There is an initial HTTP fetch error always logged and catched, even if the calls to host are succesfull.
How to reproduce
Related sub-libraries
Additional context
Thank you for your bug report – we love squashing them!
The text was updated successfully, but these errors were encountered: