search

NUKnightLab / SceneVR

A Tool for Creating Shareable, Embeddable WebVR Stories
http://scene.knightlab.com/
40 stars 6 forks source link

Be more clear about maximum upload size #77

Open sreymer opened 3 years ago

sreymer commented 3 years ago

I continually get error messages when uploading a photo to SceneVR which was shot in Apple iPhone panorama mode. This is the most recent and most common error but I've received others as well:

Error Uploading SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

I've edited and converted the photos from HEIC to JPG format. I've tried various browsers and Windows, Mac and iOS. I've been able to successfully upload non-pano photos. I don't have a clue as to what might be wrong or how to fix it.

JoeGermuska commented 3 years ago

This message typically occurs when an uncaught error occurs, resulting in a regular (HTML) web page being sent back, instead of JSON. The HTML cannot be parsed as JSON, hence the unexpected character. But we don't have any record of what happened when you see that.

Your troubleshooting strategies sound spot-on. However, I have just tried uploading a new pano shot on my iphone, as well as an example I found on the web, and both upload without error, so it's not a general issue.

Would you be willing to put your images somewhere on the internet where we could download them and see if it's something about them? One theory is file size; I thought that was being handled deliberately in the code, but I may be wrong. My iphone is kind of old, so my pano was <3MB, but I also uploaded one from the internet that was about 4MB. Still, I could see a newer iphone creating substantially larger images.

sreymer commented 3 years ago

The one(s) I've been trying to upload were 20+ MB so that may indeed be the issue. I'll try to decrease file size and see if that helps. Thanks for taking a look.

sreymer commented 3 years ago

Yes, that was the answer. Thanks!

JoeGermuska commented 3 years ago

Thanks for the follow-up! Clearly this is something we could handle better, so I've renamed this issue, and we'll leave it open as something to fix.

Things we should do: