noblox/noblox.js

[BUG] uploadAnimation(data, itemOptions, assetId) no longer works due to closed endpoint.

Opened this issue · 3 comments

iiPotatoFlamesii commented

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:

  1. Login with Cookie
  2. Call uploadAnimation with a proper data buffer and assetId; itemOptions aren't required
  3. 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.

Neztore commented

Do you know of a new endpoint to replace it?

JustValk commented
Regalijan commented

After way too much effort I think I found a replacement. It follows the open cloud asset uploading endpoint for the most part.

POST https://apis.roblox.com/assets/user-auth/v1/assets
--fe35bc7c-e1b1-4b1b-957f-ba3fad692ddf
Content-Type: application/json
Content-Disposition: form-data; name="request"

{"creationContext":{"creator":{"userId":1}},"description":"example","assetType":"Animation","displayName":"AnimSaves"}
--fe35bc7c-e1b1-4b1b-957f-ba3fad692ddf
Content-Type: model/x-rbxm
Content-Disposition: form-data; name="fileContent"; filename="asset.rbxm"

<rbxm content here>

Given the similarities it's possible that it could work via the open cloud endpoint but I have not tested it (and knowing Roblox it probably doesn't)

Edit: It does not