Rahul Goenka
Rahul Goenka

Reputation: 271

mixpanel-2-latest.min.js:9 Mixpanel error: "mixpanel" object not initialized

mixpanel-2-latest.min.js:9 Mixpanel error: "mixpanel" object not initialized. Ensure you are using the latest version of the Mixpanel JS Library along with the snippet we provide.

From the last couple of days, I am seeing this error in the console when I do inspect element in my Google Chrome. I am using the latest Chrome version 64. I am not using mixpanel. It's also showing up if I open any public website. Any idea how to resolve this error?

Screenshot of Chrome with error in developer console

Upvotes: 27

Views: 6977

Answers (7)

ScottLenart
ScottLenart

Reputation: 1210

"Free Video Downloader" is another cause.

Upvotes: 3

Dwza
Dwza

Reputation: 6565

I checked all given answere in here. All sayed to disable the "Send Anonymous Usage Statistics" checkbox in the settings....

I think hiding a problem is not solving a problem. Since there were a newer version of PageRuler (i had 2.1.2, newest is currently 2.1.3) I deinstalled the old one, reinstalled the new one and from now on, no matter if I send stats or not, error doesn't appaers anymore.

Upvotes: 1

Hardik Kalathiya
Hardik Kalathiya

Reputation: 2253

Check your extensions, for me, it was 'Page Ruler'.

No need to remove 'Page Ruler', Instead of removing do the following...

Page Ruler's options menu, and uncheck "Send Anonymous Usage Statistics".

Upvotes: 2

Tiborg
Tiborg

Reputation: 2305

Alternatively, you can go to Page Ruler's options menu, and uncheck "Send Anonymous Usage Statistics". This will enable you to continue using the extensions without seeing the error message.

Upvotes: 8

kasunb
kasunb

Reputation: 157

That's correct. The Page ruler plugin is the one who cause the console error "Mixpanel error: "mixpanel" object not initialized". Disable it and all good to go

Upvotes: 5

Luke Dohner
Luke Dohner

Reputation: 301

I started getting this error out of the blue. It was the chrome extension PageRuler. I trashed PageRuler and the error went away.

Upvotes: 11

spassvogel
spassvogel

Reputation: 3541

Check your extensions, for me it was 'Page Ruler' (https://chrome.google.com/webstore/detail/page-ruler/jlpkojjdgbllmedoapgfodplfhcbnbpn?hl=nl) that caused this error. Systematically disable all extensions until the error does not occur anymore.

Upvotes: 62

Related Questions