When I go to upload an icon, it says “Unknown Error, please try again later.” It is happening for any icon uploaded, tested on 2 PCs, for my account. Tried different browsers as well. Also tried resetting the browser.
In the console, there is a CORs error blocking it because of a domain mismatch:
Access to fetch at ‘https://www.roblox.com/places/icons/add-icon’ from origin ‘https://create.roblox.com’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. If an opaque response serves your needs, set the request’s mode to ‘no-cors’ to fetch the resource with CORS disabled.
I also experienced a similar error when trying to update the group icon for one of the groups I own, so it’s not just games this is appearing for.
This also results in a “Unknown Error, please try again later.” error, and sometimes a “Unable to update group icon” error as previously discussed in this topic.
Hi chickenputty, I tried to upload a game icon on my browser and it worked.
Do you happen to have any ad blockers installed? If so, could you try disabling them on create.roblox.com to see if that fixes the issue? From your screenshot it looks like the initial request failed, but it’s not clear why it failed.
Looks like this group icon upload bug is a separate issue that is unrelated to the original post. I’ll share it internally with our engineering team so they can take a look.
I have my adblocker disabled for roblox.com and create.roblox.com. It works on my 3rd PC which uses the same Chrome profile & extensions. It doesn’t work on my 1st or 2nd PC which uses the same Chrome profile & extensions.
Also, it fails on my 1st PC on Firefox for the exact same CORs error in console. However, works on Edge.
Now uploading on Edge does not work. I logged out of my alternative account and into my main account. Tried to upload a 1024x1024 329kb file, and received the error. It is almost like it is related to my account, the group, the icon resolution, the icon size, or something. However, the same CORs error is present in console. Maybe Edge was ok with the domain at first and now after relogging into a new account it cached the domain differently. No idea, but this is a huge slowdown for our team.
