A few days ago, the web iframe version became broken. It no longer loads assets and returns an error in the console.
index-Aa7QzLOi.js:233 [Olvy] - couldn’t setup the target element. Does it exist in the DOM?
It you open the url directly, it loads the assets correctly.
I assume this is the same problem as IOS webview is experiencing.
Hi there,
We have made a fix today that should’ve solved the original issue. Could you test if it works for you now?
It now loads the assets, but it comes up with “create an account” popup every time we save now, even though we are passing in the user id and update token.
Is there a way we can turn this off?
Similarly, is there a way of turning off. As the logic in here can eventually return the user to broken links.
Hi Peter,
We understand that it might cause some friction to close the pop-up of creating an account with Ready Player Me. However, we are a free-to-use platform and the option cannot be turned off. Settings cannot be turned off either.
I will forward your feedback to our team about it, but can’t promise any changes will be made.
I don’t think this is solved, me and others have been having issues where assets just do not load in the web version, it just has the loading animation on them but nothing ever loads even when changing to different categories of assets
Creating an avatar by clicking next does seem to save the avatar with the default outfit I was unable to change, but I get a 404 error when trying to unlock an asset for the user using the API
I have the same issues using Chrome or Firefox
Hello!
Since you are getting a 403 Forbidden error, is it possible that you don’t have the correct permissions?
Please check the API Key documentation here: Authentication | Ready Player Me
When I tested your subdomain in Chrome browser (see screenshot) it seemed to work normally, are you testing the integration or are you just testing it in the browser? What if you clear the cache and cookies or try incognito, does that help?
Hi @FireRat I will reply to the new post you did since it seems to be a different topic. This one will remain as solved!
