This issue is pretty URGENT, anyone that could help with this please? https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1765195941276409

The error is caused by how you’re importing/destructuring

tigerBackend.js

, not by

factory()

itself. The current recommended pattern is to import the named export

factory

(not

default

) and then pass it into

setContext

, e.g.:

js import("<https://your-org.cloud.gooddata.com/components/tigerBackend.js>").then(   ({ factory, TigerJwtAuthProvider }) => {     import(`<https://your-org.cloud.gooddata.com/components/${workspaceId}.js`>)       .then(({ setContext }) => {         setContext({           backend: factory()             .onHostname("<https://your-org.cloud.gooddata.com>")             .withAuthentication(new TigerJwtAuthProvider(jwt)),           workspaceId,         });       });   }, );

In your code you most likely have something like:

js const { default: factory, TigerJwtAuthProvider } = response;

That will now fail because

tigerBackend.js

no longer provides a

default

export. Instead, change it to:

js const { factory, TigerJwtAuthProvider } = response;

After this change: 1. Hard‑refresh / clear browser cache. 2. Re‑load the page and confirm the component renders instead of the

o is not a function

error. This pattern matches the current

tigerBackend.js

exports used for web component integration.[[Web components integration](https://www.gooddata.com/docs/gooddata-ui/latest/learn/web_components/#integration)]

Hi Jhonatan, We are looking into it. 👀

it seems I have found a way to fix it, removing

default: factory()

and simply using

tigerFactory()

, it looks like something changed on your end, was there a changelog or something similar, we were not aware of any changes to this, if this change was in a changelog then we need to improve our internal process, but if this wasn't communicated you should let us know when things are going to change beforehand.