-
Notifications
You must be signed in to change notification settings - Fork 18
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
v1.2.19 broke posthog.Capture #69
Comments
Yeah we auto-updated to 1.2.19 and it took down our event monitoring. Had to roll back to 1.2.18. |
It looks like they have fixed it. I will confirm later and will close this issue when I can verify. |
@migueldv90 can you confirm that this has been fixed for you? Just doing some housekeeping on our issues and I think this has been resolved, but wanted to double-check. |
Closing since I tested this myself, but feel free to reopen if I'm wrong |
@dmarticus Thank you! |
I am currently integrating Posthog in a go environment. It seems that from version v1.2.18 to v1.2.19 posthog.Capture broke. I was able to use posthog.Identify without problem but was not able to use posthog.Capture. I had to downgrade to v1.2.18 and everything seems to work as expected.
The error I am getting is -
posthog 2024/08/24 23:59:13 INFO: response 400 400 Bad Request – failed to parse request: data did not match any variant of untagged enum RawRequest
I was not able to pinpoint the specific problem. But I think it has to do with "Ability to specify uuid when capturing events" #68
The text was updated successfully, but these errors were encountered: