You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
src/utils/patchUrlMappings.ts << when using patchURL for CocosJS, the error:
"webpack-internal:///(app-pages-browser)/./node_modules/next/dist/client/app-index.js:33 InvalidAccessError: Failed to set the 'responseType' property on 'XMLHttpRequest': The response type cannot be changed for synchronous requests made from a document."
This isn't unique to our games, the Cocos samples produce the same result. Note, if you run Cocos in an iframe (with the proxy prefix) you don't need to use patchURL, however, to run without iframe due to the way Cocos loads this is necessary.
Notes: We call the DiscordSDK from the host-page NOT from within Cocos.
The text was updated successfully, but these errors were encountered:
Interesting, I'd love to take a look at this -- do you happen to have a specific example I could run and check this out with? I'm not familiar with Cocos, and hitting a lot of dead links trying to find an example project on my own.
That user has a project that can reproduce the issue (and was specifically build for Discord), that said, if you DL CocsCreator and build their hello world for Web you'll see the problem immediately.
src/utils/patchUrlMappings.ts << when using patchURL for CocosJS, the error:
"webpack-internal:///(app-pages-browser)/./node_modules/next/dist/client/app-index.js:33 InvalidAccessError: Failed to set the 'responseType' property on 'XMLHttpRequest': The response type cannot be changed for synchronous requests made from a document."
This isn't unique to our games, the Cocos samples produce the same result. Note, if you run Cocos in an iframe (with the proxy prefix) you don't need to use patchURL, however, to run without iframe due to the way Cocos loads this is necessary.
Notes: We call the DiscordSDK from the host-page NOT from within Cocos.
The text was updated successfully, but these errors were encountered: