How can I debug extension_load_error

[fabian3684386]

reproduction:

put my custom extension into app (working fine)

clicking on selections tab in Qlik header

close selection tab again

(extension reloads fine)

I get `400 Bad Request` back from the AWS SQS Queueing service with this payload:

Action: SendMessage

DelaySeconds: 10

Version: 2012-11-05 (Is this outdated, it seems old?)

{"location":{"origin":"https://qliksense*.*.com",
"pathname":"/sense/app/*/sheet/*/state/analysis"},
"eventCategory":"sense-client",
"eventName":"extension_load_error",
"properties":{"currentState":0,
"currentView":3,
"details":{"type":"third-party-code-split",
"message":"Mismatched anonymous define() module: function(t){
\"use strict\";function n(t,n){return null==t||null==n?NaN:t<n?-1:t>n?1:t>=n?0:NaN}function e(t,n){return null==t||null==n?NaN:n<t?-1:n>t?1:n>=t?0:NaN}function r(t){let r,o,a;function u(t,n,e=0,i=t.length)
... (very long cryptic JS code) ...
t.zoomIdentity=ww,t.zoomTransform=Mw}\nhttps://requirejs.org/docs/errors.html#mismatch"},
"appId":"*"},
"qlikmetricsId":"*",
"qlikmetricsVersion":"2.0.0",
"sessionId":"*",
"timestamp":1699523179404,
"userId":"*",
"version":"7.947.16",
"serviceClusterId":"*",
"deploymentEnv":"*",
"packagingEnv":"*",
"productVersion":"14.129.12"}

(internal identifiers redacted with *)

To this URL: https://sqs.us-east-1.amazonaws.com/*/de-senseclient-prod-usagemetrics

To which AWS SQS responds unhappily (because my code is too long???, it is 2MB and there is a limit of 260KB of data transfer setup there?)

{
    "Error": {
        "Code": "InvalidParameterValue",
        "Message": "One or more parameters are invalid. Reason: Message must be shorter than 262144 bytes.",
        "Type": "Sender"
    },
    "RequestId": "*"
}

What is going on?

Can I disable this feature in general to avoid these errors? Do I have to opt in? Is my JavaScript actually faulty or is it on the Qlik side?

I use a modern webpack bundler, Qlik's AngularJS, and some dependent JS libraries loaded via webpack library

[Dave_Channon]

Hi @fabian3684386 

Did you resolve this? If not, would you mind opening a support case for this? It seems you're tripping on a telemetry endpoint, and it's not something I've seen before.

Thanks!