I am able to upload other assets types, such as images. However, when I try to upload a video, I get back the following response: {'code': 'INVALID_ARGUMENT', 'message': 'Actual price (2000 Robux) is larger than expected price (0 Robux).'}
I cannot find any documentation on this issue. I thought of including a header of “expectedPrice” but it didn’t work. I do have enough Robux in my account.
Would appreciate any insight on working around this issue!
I managed to add the expectedPrice field. However, now I get back a new response - I didn’t copy it but it looks something like {path: abcd-efgh-ijkl, Done: False}
The Done: False section didn’t look very promising! I tried it a few times, in hopes it would work randomly, but now I’m getting: {'code': 'RESOURCE_EXHAUSTED', 'message': 'User does not have available quota for asset upload. Please retry later'}
The problem now is that the videos I’ve supposedly uploaded don’t show anywere? They aren’t visible on my Development Items tab. So I’m not sure if I’ve actually uploaded them or not, but either way my quota has been used.
[EDIT 10HRS LATER]: Videos have now uploaded. Thanks a lot!]
Ooh, interesting. So was this essentially saying the upload request was completed but the website still needed to moderate the asset? Or is it slightly different?
I didn’t keep track of the endpoint path - was I meant to use this to complete the request or will it still complete in the background? What do I do if I didn’t note down the path?
Thanks, and sorry for tons of questions. I’m finding the documentation confusing, and I’m hoping the videos aren’t lost somehow!
We made our new upload APIs return long running operations in order to support larger uploads. We process the upload in the background and you can check the status of the upload with the operation path given to you.
If you didn’t note down the operation path, the upload would happen as normal. If it’s successful, the asset will show up in your creations. If it fails, querying the operation path is needed in order to see what went wrong.
I can work with our team to try to make the documentation more clear on this!