Hello,
we have an issue with JPEG Attachments on Feature Services in Enterprise 11.2 not having a preview in Popups. It seems to be due to the REST API not being able to produce a smaller image preview when the "w" parameter is defined in the request (see https://developers.arcgis.com/rest/services-reference/enterprise/attachment-feature-service/). We have found this issue to be appearing with images from Samsung Phones, especially with Android 14. The REST API returns this error:
JFIF APP0 must be first marker after SOI
There are some old threads regarding this error message and they seem to hint towards the EXIF data of the images:
https://stackoverflow.com/questions/55150857/reading-jpeg-or-gif-metadata-with-javax-imageio
https://github.com/haraldk/TwelveMonkeys/issues/428
Interestingly, when we download an attachment where the preview doesn't work, save a copy of the image with the Windows default image viewer (and thereby modifying the EXIF data) and add the image as an attachment again, the preview works. We also don't have this problem with the original image added as an attachment to a feature layer in ArcGIS Online.
Has anyone had the same issue or can confirm it?
Thanks
Hi malte,
we have the same issue with Samsung mobile phones (Android 11 and 13) in Enterprise 11.1.
Images taken with iOS devices do not cause any problems.
We collect data and photos with Field Maps. In MapViewer popup the attached photos are only shown as linked container with text like "photo1". By clicking that container a new tab in the browser opens showing the image.
I took a look at the jpg files with Notepad++
Samsung jpg starts like that ÿØÿáâExif MM *
iPhone jpg starts like that ÿØÿà JFIF H H ÿá
Other devices I can not check as we only use iPhones and Samsung mobile devices.
Any solution or hint as where to change Enterprise Portal configuration our files would really be appreciated.
Hi,
I came across the same behaviour in Enterprise 11.1 with Samsung devices, attachments captured with iPhones worked fine. Confirmed this is now BUG-000170994
According to BUG-000170994 it should be resolved, but we have now 11.4 installed and this problem still persists. So what has been fixed? We are using Samsung mobiles, as someone above wrote - on iOS this does not occurs.