With SDK 1.8.5, you applied changes on the language handling (i18n changes mentioned in your change log post)
I have correctly applied changes on the code to load the specific languages and apply customization, this is fine.
Unfortunately, for local versions, instead of using the custom lib path specified by the following line:
Yes, everything from the lib directory is embedded in our docker image and available on the custom hosted path of the application: wasm, js, css, audio & json files.
I already updated the code to use ZoomMtg. The application works when using CDN but not local (reported error above)
so you will see send two request en-US.json
Iâm not sure whethe you say first request en-US.json not use you specific path. if yes, you can ingore this request.
Thank you for your reply.
So if i understand correctly, right now there is no way to avoid this 404 not found when we do not allow to access node_module (no public access). In our case, yes we do not make node_module public on our application, and publish public resources on the custom URL instead (and only there)
If this is coming from the cookie, is there a future patch to âfixâ it and use the custom library path instead so that no more 404 is generated when starting the zoom web SDK ?
About breaking changes, i realize that a ZoomMtg.reRender() was missing after loading the languages, therefore not displaying in Japanese but English when JP is the default language.
So, this is still an issue (minor one) since it generate 404 for nothing, but definitely not a breaking change anymore.
Thank you again for your detailed answer.