Calling Bynder GetAssetService().UploadFileAsync() about bynder-c-sharp-sdk

[greenrya]

Hi @greenrya The error that you receive is being returned when trying to finalize the upload. If this issue does not happen with all uploads it could also indicate that there might be something wrong with the file itself that you're trying to upload, or, that the chunk(s) have not all been uploaded yet. What happens if you retry?

Like support did say we are going to move to the Files Service upload hopefully soon, this will hopefully solve any upload issue with the current method. We are awaiting on other teams to give the greenlight to merge the PR we have ready for this.

Any update on merging this PR into our Sandbox instance?

[TimBloembergen]

Hi @greenrya The error that you receive is being returned when trying to finalize the upload. If this issue does not happen with all uploads it could also indicate that there might be something wrong with the file itself that you're trying to upload, or, that the chunk(s) have not all been uploaded yet. What happens if you retry?

Like support did say we are going to move to the Files Service upload hopefully soon, this will hopefully solve any upload issue with the current method. We are awaiting on other teams to give the greenlight to merge the PR we have ready for this.

[greenrya]

@TimBloembergen It happens more frequently in our instance now. The file uploads just fine from the UI we need to be able to rely on the upload process it is very important to us. What is being done to help resolve this we need help our sandbox URL is https://playlsisandbox.getbynder.com

SendHttpRequest - Status: InternalServerError Body: {"message":"Upload not ready","retry":1,"success":false} Headers: Connection = keep-alive, Date = Wed, 17 Nov 2021 16:21:43 GMT, Server = nginx, Cache-Control = no-store, must-revalidate, no-cache, X-Frame-Options = SAMEORIGIN, Access-Control-Allow-Origin = *, Access-Control-Allow-Credentials = true, Access-Control-Allow-Methods = GET, POST, PUT, DELETE, OPTIONS, Access-Control-Allow-Headers = DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Authorization,X-Bynder-Integration, X-Cache = Error from cloudfront, Via = 1.1 a2165b66922b78c24eb18ccc5d845335.cloudfront.net (CloudFront), X-Amz-Cf-Pop = SFO53-C1, X-Amz-Cf-Id = 6wouqhcfKsYgNluLCw7SYjQ5zKw7AB1u5XKQY6V_bxeNBX8mByfGJw==

[greenrya]

Still getting this message frequently and retries fail too. What is the status on File Services?

2022-03-18T11:36:38.017 [Error] Executed 'SyncModel' (Failed, Id=676aee46-36e8-4a9a-8fc0-2282374ea247, Duration=60591ms)SendHttpRequest - Status: InternalServerError Body: {"message":"Upload not ready","retry":1,"success":false} Headers: Connection = keep-alive, Date = Fri, 18 Mar 2022 11:36:37 GMT, Server = nginx, Cache-Control = no-store, must-revalidate, no-cache, X-Frame-Options = SAMEORIGIN, Access-Control-Allow-Origin = *, Access-Control-Allow-Credentials = true, Access-Control-Allow-Methods = GET, POST, PUT, DELETE, OPTIONS, Access-Control-Allow-Headers = DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Authorization,X-Bynder-Integration, X-Cache = Error from cloudfront, Via = 1.1 f180978007f83adae5595134610a89fe.cloudfront.net (CloudFront), X-Amz-Cf-Pop = LAX50-C4, X-Amz-Cf-Id = qOtJpIPFL9m9ayC6JZNAbDMNJypLe-SvAdZUqFca0Gfjr6gM3GphEQ==

[meghuizen]

I'd prefer if the FileService upload branch is being pulled in to the master branch and a new release being created. Since this removes the polling and creates a way more stable file upload process.