ExifInterface: Invalid image.

[hpdx]

11-29 14:38:58.418 27599-27644/? W/ExifInterface: Invalid image.
java.io.IOException: Invalid marker: 89
at android.media.ExifInterface.getJpegAttributes(ExifInterface.java:1612)
at android.media.ExifInterface.loadAttributes(ExifInterface.java:1335)
at android.media.ExifInterface.(ExifInterface.java:1053)
at com.facebook.imagepipeline.producers.LocalExifThumbnailProducer.getExifInterface(LocalExifThumbnailProducer.java:136)
at com.facebook.imagepipeline.producers.LocalExifThumbnailProducer$1.getResult(LocalExifThumbnailProducer.java:103)
at com.facebook.imagepipeline.producers.LocalExifThumbnailProducer$1.getResult(LocalExifThumbnailProducer.java:97)
at com.facebook.common.executors.StatefulRunnable.run(StatefulRunnable.java:45)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)

[massimocarli]

Hi @hpdx ,
Can you provide us the image Url please?
Thanks

[ChenSiLiang]

same issue.
@massimocarli It seems this native method return null
nativeGetRawAttributesFromFileDescriptor() in ExifInterface.class.
So handleRawResult() return false and it call getJpegAttributes(in),in fact it is not a JPEG

[lambdapioneer]

@ChenSiLiang can you provide us with a sample image file that shows the described behavior? That would allow us to verify the fix and add unit tests to avoid regressing this.

[ChenSiLiang]

sure, like this.

tips:fresco 0.14.1, nexus 5x, android 7.1.1

[hzw1199]

I find this to be solved in fresco 1.0.1

[erikandre]

Closing issue as the problem is reported to be solved :)

[kirwan]

I don't think this was actually solved as it's been reported again in #1760.

The key thing which I think was missed before is that the image is a PNG and EXIF data is only available in JPEGs.

[farwayer]

@kirwan I just trapped into this issue with React Native in combination with CodePush. Is any chance new version with fix will be released soon?

[kirwan]

This is now fixed in Fresco 1.4.0. @farwayer if this is causing a problem for you with React Native, we'll need to get that updated to use 1.4.0.