Failure to upload files: "Invalid import ID" from polling for status

[gediminasmorkys]

I am using https://github.com/Bynder/bynder-java-sdk/blob/master/src/main/java/com/bynder/sdk/service/upload/FileUploader.java#L70 to upload files to Bynder.

I have been successfully uploading files with release 2.2.20 for three months until 2024-03-16 00:51:00 EET.

Since then, without changing the release version of this library, whenever I try to upload a file to Bynder, I get the following result:

• the library makes a call to https://bynder.docs.apiary.io/#reference/upload-assets/4-finalise-a-completely-uploaded-file/finalise-a-completely-uploaded-file
• the library includes the received importId = 2799586B-1DC6-443E-842CAFCE3ECDEE27 as an item in "items" of the next call, https://bynder.docs.apiary.io/#reference/upload-assets/5-poll-processing-state-of-finalised-files/retrieve-poll-state
• Bynder responds with Response{protocol=h2, code=400, message=, url=https://[ourBynderHost]/api/v4/upload/poll/?items=2799586B-1DC6-443E-842CAFCE3ECDEE27/} {"message":"Invalid import ID","statuscode":"400"}
• the Bynder internal work is a black box to me. But it surely seems like there is an issue between finalising an uploaded file, and polling for status using a resulting import id.

I have been advised to create this ticket here, so Bynder support can reference it.

To be honest, this feels way more of a Bynder's backend issue than the library's inner workings.

But maybe you can confirm that the library still works for uploading files?

Edit1: seems that small files that do not require chunking are uploaded just fine.
Edit2: it looks like the conversion process in Bynder's backend could take longer than the longest possible polling process in this library. I don't really know if Bynder's backend has a timeout on "finalize upload" activities. But if it does, it would make sense to tie the polling to that timeout, and instead of "Invalid import ID" the error message could communicate the cause of this issue better.

[rickvolbeda]

Noticed the same behaviour recently in an implementation I am currently working on. Bynder is responding with a bad request code and the message is saying "Invalid import ID". It seems to me that the forward slash "/" at the end of the URL is causing the issue. When you call Bynder with the trailing slash manually you get "400 - bad request", when you remove the trailing slash you get the proper response.