This started about 10 days ago, I thought it was a server issue before realising it was a client one. Images in posts and comments fail to load with the following error

Unknown error
Failed to create image decoder with message 'invalid input'Input contained an error.

It affects 99% of images and I haven't been able to discrern a pattern in the images that load successfully. They have the same formats and URLs as the images that fail to load.

This started happening on 1.72.x, but updating to 1.73.0 has not helped.

I have looked at logcat and found that an error is generated that seems to be related to mime type detection, or heif format loading. Perhaps some changes were done to that code that don't agree with my phone's android 11 install. I haven't done any changes to my phone, and it worked before, so I assume it is a change in the app that triggered this behaviour.

Here is the relevant logcat output when trying to view a jpeg image:

I HeifDecoderImpl: HeifDecoder* createHeifDecoder()
I HeifDecoderImpl: HeifDecoderImpl::HeifDecoderImpl()
I MMParserExtractor: Created(0xb4000078c8a66000)
E MM_OSAL: FileSource::FileSource
E MM_OSAL: FileSource::FileSource m_bEveryThingOK 1
E MMParserExtractor: FileSourceWrapper::New Init returned -1004
E MMParserExtractor: readMetaData - FileSourceWrapper::New returned NULL
E MMParserExtractor: MMParserExtractor::countTracks no tracks
W Utils: did not find mime type
W ExtendedUtils: did not find mime type
W Utils: did not find mime type
W ExtendedUtils: did not find mime type
I HeifDecoderImpl: HeifDecoderImpl::~HeifDecoderImpl()
E ErrorUtils: Unknown throwable android.graphics.ImageDecoder.DecodeException
E ErrorUtils: android.graphics.ImageDecoder$DecodeException: Failed to create image decoder with message 'invalid input'Input contained an error.
E ErrorUtils: at android.graphics.ImageDecoder.nCreate(Native Method)
E ErrorUtils: at android.graphics.ImageDecoder.createFromFile(Unknown Source:19)
E ErrorUtils: at android.graphics.ImageDecoder.access$600(Unknown Source:0)
E ErrorUtils: at android.graphics.ImageDecoder$FileSource.createImageDecoder(Unknown Source:2)
E ErrorUtils: at android.graphics.ImageDecoder.decodeBitmapImpl(Unknown Source:1)
E ErrorUtils: at android.graphics.ImageDecoder.decodeBitmap(Unknown Source:2)
E ErrorUtils: at coil3.decode.b.a(r8-map-id-91472c89a467098dfb73dac40527f712a4c3af1dbf42a37f171cabd4500276b3:84)
E ErrorUtils: at coil3.intercept.a.a(r8-map-id-91472c89a467098dfb73dac40527f712a4c3af1dbf42a37f171cabd4500276b3:160)
E ErrorUtils: at coil3.intercept.EngineInterceptor$execute$executeResult$1.w(r8-map-id-91472c89a467098dfb73dac40527f712a4c3af1dbf42a37f171cabd4500276b3:57)
...

There's more obfuscated calls in the stack trace that I can include if helpful.

Image links on lemmy used to be nice and short(ish), but now that they get proxied they look pretty ugly - especially if an image gets proxied through multiple instances, which is something I've seen quite a few times. I assume this is simply because someone copied a proxied link on one instance and posted it on another.

Would it be possible to add an option to un-proxy the link before copying it? Not sure if this would work better as a global setting or another context menu item, but I would find it very useful.

Example:

Normal: https://lemmy.ml/pictrs/image/288a95d3-b040-475c-9b8c-6fe4fe14fcac.png

Ugly: https://lemmy.zip/api/v3/image_proxy?url=https%3A%2F%2Feurope.pub%2Fapi%2Fv3%2Fimage_proxy%3Furl%3Dhttps%253A%252F%252Flemmy.ml%252Fpictrs%252Fimage%252F288a95d3-b040-475c-9b8c-6fe4fe14fcac.png

And thank you for the great app.