At the first launch, it is several assets, when the page is reloaded, it is spam of the same error on most assets.
Weirdness in two things:
If you publish the build - there are no errors.
It starts happening when I add code for dynamic loading script (checking the advertising sdk, code below).
// Create a new script element
var admixerLoader = document.createElement('script');
// Set script attributes
admixerLoader.src = 'https://some.js';
admixerLoader.async = true; // tried without
admixerLoader.setAttribute('someAttribute', '//some-attribute/');
//some more attributes set
// Append the script element to the document's head or body
document.body.appendChild(admixerLoader);
Unfortunately no, I’m not sure I have permission to share the relevant links.
I will also add that:
Сleaning the Application Storage (and, accordingly, re-login in playcanvas) - the first launch after that has fewer of these 403 errors
I would still like to solve this problem. As I understand it, the imported advertising script changes something in the data and breaks my “authorization”. Can you tell me what to look for there? Local/Session storage? Cookies?
Is it in cookies? After looking at the minified script (advertising SDK) that is being imported, I did not find interaction with pc_auth there, or could cookies be damaged in some other way?
When I launched your project, my other projects stopped loading as well. I then cleared the cookies for last hour, and those are good again. So I’d say a cookie.