ReferenceError: dmx is not defined

[karh]

We have a decent amount of events logged by Sentry where 'dmx is not defined'.

I can reproduce the error by simply removing the appconnect include on the layout page.

We can't seem to puzzle together why this happens. I thought perhaps only old browsers but there's also recent browsers in there:

@patrick Any idea when this could happen?
On replays we can see that all the bindings are there and a moving mouse so it does seem to really affect certain users:

We're on Node.

[Apple]

@karh

I can reproduce the error by simply removing the appconnect include on the layout page.

Show how you include

[karh]

Just the default way

[karh]

Bump

[George]

well check the devtools network tab to see what errors and files are missing

[karh]

As mentioned in the OP: we're recording this using Sentry. I can't reproduce it locally other than removing appconnect.

Would love some input on this

[Apple]

At what line is this error thrown? Check if you can find the line number

[karh]

It's thrown in all the appconnect extensions

[ben]

It looks like Sentry is active before dmxAppConnect.js has been fully loaded.

[karh]

Thanks for the input Ben, I'm in doubt this is happening:

1. As per the sentry documentation, you should load it before all other scripts JavaScript | Sentry for JavaScript
2. I see that it's actually set up right underneath the dmxAppConnect.js
   
   
   (not following Sentry's instructions, so I'll move it up now and see if that helps)
3. If that's the case then wouldn't it consistenyl be a problem?
4. As far as I understand Sentry, it gotta be set up to catch errors - and it shouldn't catch those errors if they are not actually happening. So if this is caused by Sentry loading before dmxappconnect, that shouldn't impact that. It should just send all subsequent errors to Sentry.

Someone with a good idea on debug logs to add to figure this out?