Hi @spandit, unfortunately not at the moment, i’ve kept source map for the time being but a little concerned this will be publicly exposed
Looks like you all are using Angular, please see the Angular Sample app and how I am including the files:
Let me know if that helps!
We are using React with
react-scripts build scripts. If there is no React example on how to fix it, can you explain what you are trying to do in the angular case?
Have you included the required files? It should also work in React:
I faced same problem but not fixed yet.
Please help me
We are also facing the same exact problem with the exact same error in production.
Can you please help me.
We are using React with
react-scripts build scripts.
Can you please provide a github repo with the error so I can reproduce and debug locally?
Here, is the github repo for a react app where I have replicated the error if you follow the readme file.
My github repo
I was able to reproduce the issue using your repo, however, I was not able to solve it. This seems to be an issue with react or the way it optimizes it’s build.
Like @grahaampeterson said, it works when enabling source maps.
Maybe this Stack Overflow will help:
I will talk to our Web SDK engineerings to see if this is the reason it is not working in a production build. (CS-1971)
Thanks for checking it out.
I hope it gets solved soon
Happy to help!
I will keep you updated!
Any update about this issue?
waiting update for this issue
i use react-app-rewired for solved this issue
I am also facing the same issue in angular , Please any one found fix please help me,
Because, I am facing big problem in production from my clients.
I was not able to reproduce this issue using GitHub pages and the Angular sample app here with the built version in /docs:
$ ng build --prod
Was this fixed in Zoom Web SDK version 1.8.0 released today? I was having a similar issue yesterday:
nuxt Error while "mounting" app: SyntaxError: Unexpected end of JSON input
…while using SDK version 1.7.9, npm, nuxt, vuejs. It worked locally, but I got the above error in production.
I spent most of yesterday doing fresh installs of the SDK, as well as all packages from scratch, thinking something was corrupt or cached. When I did the same today, I noticed I was now installing 1.8.0, and it finally worked on my production server.
To confirm, you are no longer seeing this issue in version 1.8.0?
Correct. But I’m curious if this was actually addressed in the upgrade, or if it’s just a coincidental outcome of that particular removal + re-installation process I did. I also noticed the min requirements for some dependencies had changed as well, so it could be related to the dependencies as well.
Let me find out.