Cannot read property 'track' of undefined about gatsby-plugin-segment-js HOT 8 OPEN

this is weird. do you have an ad blocker? which browser are you using. how does this work on production, or you only see the issue on dev? when you check for window.analytics in your chrome console, what happens?

please let me know the above, or if the issue is solved, please comment what the fix was. thanks!

from gatsby-plugin-segment-js.

I had the same issue, and window.analytics returned undefined for me in the Chrome console. However, this was only on localhost, and it works fine on production.

from gatsby-plugin-segment-js.

what about when you do yarn build ... i assume it works then?

and you've checked incognito browser, with no ad blockers, right?

from gatsby-plugin-segment-js.

I also had this issue, window.analytics returned undefined, I've tried yarn build but no luck

from gatsby-plugin-segment-js.

just in case someone comes across this, it means you probably don't have a DEV key defined. the prod key will only run in production, local host is dev environment.

from gatsby-plugin-segment-js.

I hit the same issue, until I wrapped my window.analytics.track in a if (window.analytics) conditional.

It looks to me like the analytics.js script isn't being loaded into the page header. This is true even on production build. When looking at the chrome console (adblocker disabled), I have no window.analytics options available.

from gatsby-plugin-segment-js.

I had this problem because I copied the code snippet from the docs which contains a junk code snippet:

customSnippet: '!function(){var analytics=window.analytics||[];...;analytics.load("${writeKey}");analytics.page();}}();'

I had to remove that. 😦

from gatsby-plugin-segment-js.

Without a valid env variable, analytics doesn't load; Set NODE_ENV to production or development

export NODE_ENV=production

or

export NODE_ENV=development

from gatsby-plugin-segment-js.