Hey there, I am also getting following error. It u...
# gooddata-cloud
n
Hey there, I am also getting following error. It used to work until yesterday Uncaught SyntaxError: The requested module 'https://***.cloud.gooddata.com/components/tigerBackend.js' does not provide an export named 'default'
j
Hi Nagaraja, Thanks for reporting this. We are sorry for the troubles. We are currently looking into this with higher priority. Would you be able to provide screenshots from devtools? Console tab / Network tab... optionally even HAR File?
n
image.png
image.png
earlier working script is return ` import { setContext } from "${goodDataHost}/components/gooddata.js"; import factory, { TigerTokenAuthProvider } from "${goodDataHost}/components/tigerBackend.js"; const backend = factory() .onHostname("${goodDataHost}") .withAuthentication(new TigerTokenAuthProvider("${environment.goodData.authToken}")); window.setGoodDataContext = (workspaceId) => setContext({ backend, workspaceId }); if (!window._gdInitialized) { window.setGoodDataContext("${defaultWorkspace}"); window._gdInitialized = true; } `;
we are using authentication token and dynamic workspace based on the page user in
j
Thank you very much for the information. We are working on it.
n
j
We have already liaised with our engineering and we are working on the fix. We will keep you updated.
The fix has been deployed. Could you please check on your end?
n
Still giving same error. I have used InPrivate mode to test
j
thanks for checking, we will get back to you
f
Hi @Nagaraja Joisa May I suggest the following edit:
Copy code
import factory, { TigerTokenAuthProvider } from "${goodDataHost}/components/tigerBackend.js";
Change it to:
Copy code
import { tigerFactory. TigerTokenAuthProvider } from "${goodDataHost}/components/tigerBackend.js";
This way we avoid the
default
import, by naming it. It helped workaround the issue on my own environment.
n
@Francisco Antunes: Thanks it is working.
🙌 1
f
That’s great news! We apologize for the issues, and we’ll implement a fix ASAP. I’ve already discussed with our engineers, and the fix will not break the workaround that you applied, so everything should continue to work. We’ll let you know once we have more news.
Hi @Nagaraja Joisa our engineers have implemented a fix for this issue. It should not affect the workaround you applied to minimize it yesterday, so there is no action required from you. Thank you! 🙂
✅ 1