RuntimeException: Invalid Content-Range header when device locale is set to arabic

[omjimehrotra]

Here is the error stack trace.

E/DefaultRequestProcessor: Unexpected exception for request ff49ae42-aed4-463b-96c2-c4a1d875d8cc.
java.lang.RuntimeException: Invalid Content-Range header
at com.cloudinary.android.UploaderStrategy.callApi(UploaderStrategy.java:143)
at com.cloudinary.Uploader.callApi(Uploader.java:34)
at com.cloudinary.Uploader.uploadLargeParts(Uploader.java:212)
at com.cloudinary.Uploader.uploadLarge(Uploader.java:143)
at com.cloudinary.android.DefaultRequestProcessor.doProcess(DefaultRequestProcessor.java:197)
at com.cloudinary.android.DefaultRequestProcessor.processRequest(DefaultRequestProcessor.java:89)
at com.cloudinary.android.MediaManager.processRequest(MediaManager.java:367)
at com.cloudinary.android.AndroidJobStrategy$UploadJob.onRunJob(AndroidJobStrategy.java:203)
at com.evernote.android.job.Job.runJob(Job.java:109)
at com.evernote.android.job.JobExecutor$JobCallable.runJob(JobExecutor.java:151)
at com.evernote.android.job.JobExecutor$JobCallable.call(JobExecutor.java:136)
at com.evernote.android.job.JobExecutor$JobCallable.call(JobExecutor.java:119)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:764)

[d-mendoza]

Hi @omjimehrotra,

To better assist in diagnosing this issue, can you provide us with the following:

1. The upload command use
2. The parameters passed into the upload call

[omjimehrotra]

Hi @d-mendoza

Here is my cloudinary upload command:

MediaManager.get().upload(filePath).callback(uploadCallback)
.unsigned(AppConstants.CLOUDINARY_UPLOAD_PRESET)
.option("resource_type", "auto")
.dispatch();

[d-mendoza]

@omjimehrotra Thank you for pointing this out! Our team is looking into it.

[MaxBayne]

@d-mendoza

any help or fix for this bug

thanks

[d-mendoza]

@MaxBayne It's on our dev teams todo list. I'll update when we'll have any insights.

[omjimehrotra]

Any Update on this issue?

[MaxBayne]

no still issue

…

On 5/11/18, omjimehrotra ***@***.***> wrote: Any Update on this issue? -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #57 (comment)

[yakirp]

Hi guys, I hope that we will fix this issue soon, I will update.