-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RuntimeException: Invalid Content-Range header when device locale is set to arabic #57
Comments
Hi @omjimehrotra, To better assist in diagnosing this issue, can you provide us with the following:
|
Hi @d-mendoza Here is my cloudinary upload command: MediaManager.get().upload(filePath).callback(uploadCallback) |
@omjimehrotra Thank you for pointing this out! Our team is looking into it. |
any help or fix for this bug thanks |
@MaxBayne It's on our dev teams todo list. I'll update when we'll have any insights. |
Any Update on this issue? |
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)
|
Hi guys, I hope that we will fix this issue soon, I will update. |
any update on this one? Getting this bug also with other locales .. |
make sure your file length is not 0 |
Any update on this issue? I am facing the same issue with Indian languages(Marathi/mr) |
Hi all, and especially to Siddarth who posted today- If you're still seeing this issue, may I ask which version of the SDK you're using and for an updated example? This issue is still open at the moment but I've checked with the SDK team and we believe this may be resolved in v1.24.1 or later of our Android SDK due to changes in the underlying Java library, the version of which was updated in #67. This was a change which forced the en-US locale for the chunked upload calls which should have worked around the issue here |
Hi igy, |
Hi Siddarth - can you please try with v1.24.1? Or preferably with the current version, v1.26.0 ? |
I've tried using version 1.24.1 and 1.26.0 and I'm still having this issue, even if I try to change to locales such as en-US. Is there any solution for this yet? Would really appreciate some help with this as the library is unusable for me with this issue. |
@luke537 The fix was introduced on 1.24.1, and from my understanding from the thread, it works for @Siddharthflo as well. Are you not able to upload anything to Cloudinary, regardless of the locale? |
@idobarnoam Currently, I am not able to upload anything to Cloudinary from Android. Please see my flow below:
Basically, all I'm doing is taking a photo and passing the URI of the photo to Cloudinary to upload. Here are the Android versions: |
@idobarnoam @yakirp Hi, is there any update on this? |
@luke537 Sorry for the response delay. What I'm understanding is that currently, no upload is possible on your project regardless of locale. Is that the case? I'm asking since if you can't upload at all it might be a different issue not related to locale so it might be best to open a request at support@cloudinary.com with the relevant details. This would also allow faster replies and resolutions. |
Hi, is there any update on this? |
Hi @darothub |
Ok. I was trying to upload an image from android studio. I used the manifest config file to initialized MediaManager. Then the following
and all I get is Invalid Content Range header error Sincerely, I have since moved to firebase but thought Cloudinary would be handy |
@darothub Can you please share the original file you tried uploading? Was it taken through the camera or uploaded from a local file system? If you could also share your cloud name I will be able to check the logs. You can always raise a support ticket here: https://support.cloudinary.com/hc/en-us/requests/new if privacy is a concern. |
Hi @aditimadan-Cloudinary sorry for the late response. Yes the image is taken through the camera and a local file system. Currently I'm using my personal account(cloud name: carflux) for test. It turns out we are still interested in using Cloudinary. So we will getting a paid storage if all works well. Find the image url below: |
Hi @darothub, Can you please check and tell us what is the device current language? |
@michalkcloudinay Apologies once again for replying late. I have been handling a lot but still need to use your service. The device current language is English. Thanks in anticipation |
@michalkcloudinay @aditimadan-Cloudinary We have purchased the official cloudinary account for our application. Any update on this issue? |
@darothub In order to investigate your issue, can you please open a ticket here: https://support.cloudinary.com/hc/en-us/requests/new? |
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)
The text was updated successfully, but these errors were encountered: