2.10.0 Doesn't Send Events with Identical Initialization?

Hi all,

I’m looking forward to trying out the new features of 2.10 (especially useBeacon!)

However, I was hoping I’d be able to just swap out 2.10.0 for 2.9.2, and get up and running. For some reason, I can’t get 2.10.0 to start sending events.

I uploaded these two examples, which just takes the snippet from the Setup Guide (and point at a dummy endpoint), and the only thing I change is the 2.10.0 link for the 2.9.2 one

https://snowplow2100test.netlify.com/

(in the 2.9.2 version, you can see the attempt to GET from the endpoint in the Network panel; in the 2.10.0 version, I don’t see anything)

There must be something I’m missing with initializing 2.10.0, right? Sorry if it’s something obvious

Thanks, Scotty

[mhadam]

I’m waiting on 2.10.1-rc2 to deploy, but it’s updated to include a workaround for Chrome (it won’t fix Beacon API, but I’ll catch the exception and it should fallback to POST requests). As much as it’s great that you’re able to make it work with plain/text, I can’t expect everyone else to set up their tracking pipeline to accommodate that. You’re right though this seems like the Chrome team is (bizarrely) behind on this bug.

[pearsonhenri]

Just wanted to peep from the peanut gallery to say thanks for chasing this down. This was driving me bonkers when I tried to track down what was happening. Very arcane bug. Appreciate the quick patch @mhadam!