Karl-Aksel Puulmann
Karl-Aksel Puulmann
The only thing really tackleable without it being a breaking posthog-js change is rollup + console.log changes. Everything else in this list is breaking in the sense of either: 1....
Hey! I'm unable to reproduce this: Could you include information on: 1. How you're initializing posthog 2. Code around the `reset()` call?
Happy to fix once https://github.com/PostHog/posthog-js/pull/87 lands :)
In this case, you can work around this by call `.opt_in_capturing()` in the loaded callback. See an example with identify here: https://posthog.com/docs/integrate/client/js#identifying-users
Oops - https://github.com/PostHog/posthog-js/pull/91 is indeed correct.
I was not able to reproduce this - #109 introduces some integration tests to this effect as well. Mind testing it out once that PR lands?
The PR is now live, on [email protected] and on app.posthog.com. @yakkomajuri
Actually, sending data via XHR GET would fail for the same reason. The bug is the same for both - we should put the data into the URL via `args`:...
Might be related to https://github.com/rrweb-io/rrweb/issues/591 - @alexkim205 or @rcmarron worth investing into fixing this/doing an upgrade?
The sessions query indeed aggregates based on distinctId not personId. Proof: https://github.com/PostHog/posthog/blob/master/ee/clickhouse/sql/sessions/list.py#L95-L97 Meta-issue required to be solved here is what even is a session and what usecases does it serve:...