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
Describe the bug uploadAnimation(data, itemOptions, assetId) no longer works correctly when using assetId to overwrite/update an existing animation. The roblox.com/ide/publish/uploadexistinganimation endpoint seems to have been shutdown.
To Reproduce
Steps to reproduce the behavior:
Login with Cookie
Call uploadAnimation with a proper data buffer and assetId; itemOptions aren't required
Error occurs
Additional context
Further study shows that the roblox.com/ide/publish/uploadexistinganimation endpoint is returning 404 errors. I personally have tried multiple other endpoints for overwriting/updating existing animations, but none work. Most return a 500 error, but some will return a 400 error saying that the asset type isn't allowed.
My best guess is that Roblox switched to a different uploading endpoint for overwriting animations, and likely will have to be pulled from Studio in order to get the new endpoint.
The text was updated successfully, but these errors were encountered:
Describe the bug
uploadAnimation(data, itemOptions, assetId)
no longer works correctly when using assetId to overwrite/update an existing animation. Theroblox.com/ide/publish/uploadexistinganimation
endpoint seems to have been shutdown.To Reproduce
Steps to reproduce the behavior:
uploadAnimation
with a proper data buffer and assetId; itemOptions aren't requiredAdditional context
Further study shows that the
roblox.com/ide/publish/uploadexistinganimation
endpoint is returning 404 errors. I personally have tried multiple other endpoints for overwriting/updating existing animations, but none work. Most return a 500 error, but some will return a 400 error saying that the asset type isn't allowed.My best guess is that Roblox switched to a different uploading endpoint for overwriting animations, and likely will have to be pulled from Studio in order to get the new endpoint.
The text was updated successfully, but these errors were encountered: