Frederik Rajiv

Facing the same issue on our Vue.js setup. Same stack trace as shown by @lukebelbina Currently, the issue only appears in our staging environment.

@pauldambra Yes, the error seems to originate from the `_execute_array` function. In my understanding, this function sends over events triggered before Posthog got initialized. I placed a breakpoint in the...

```js import posthog from 'posthog-js' export default { install(app) { /** * @type {import('posthog-js').PostHog} */ const instance = app.config.globalProperties.$posthog = posthog.init(import.meta.env.VITE_POSTHOGKEY, { api_host: 'XXXX', // Reverse proxy hosted on Azure...

Browser also seems to affect the issue. On Safari, the error triggers consistently on each page load. On Chome only occasionally .

@pauldambra Correct, not on production Building for production and serving locally also triggers the error. Some `$autocapture` events also trigger the event, so not exclusively `$pagecapture` Really a head-scratcher 🤯

Turns out it was an accidental double initialization from the JS SDK. Once through Google Tag Manager, and once through Vue.

+1