It’s kind of in a half fixed state right now as I rushed v420 out but basically Flutter (what Connect is written in) doesn’t support .avif images by default so I need to add a special library to handle it. There should be a proper fix coming in 421.

Hi, I can definitely look into this more. Can you make a post detailing the issue via the ‘Report a bug’ option in Settings (top right three dot menu). Thank you.

This stack trace was what I needed, thank you for posting it. Cheers!

Hi, this issue should now be resolved on the latest version of Connect (v420). Thank you for the report.

Is the issue still occuring for you on v418? Thank you.

Is this still happening for you on v418? I can take more of a look if you are still seeing it.

Okay thank you, I haven’t been able to reproduce the issue so it’s a bit of a guess. I pushed another update if you’re on the beta track.

Hi, this issue should be fixed in v417. If it’s still occurring please let me know.

Hi, thanks for the report and I’ll take a look at this today.

Edit: This issue should now be resolved on the latest version.

Thanks that is helpful, this should be patched in the next release. Cheers!

Is it happening on a specific video for you? I tried a couple and didn’t see an issue. Thank you for the report!

If you’re on beta it should be live now! If you’re on the main release channel most likely tomorrow.

I’ll add support for this specific Piefed instance tonight and more generally improve the detection of new/unknown Piefed instances. Should be coming in v412. Cheers!

Hi, within Settings can you go to the three dot menu (top right) then Report Bug and copy and paste the text that it prefills?

Thanks for the report, I’m taking a look at this now and will include it in the next beta release (tonight). Cheers!

Google Play will store and attempt to restore the storage I believe. On my device I long-press on the app icon -> Click App Info -> Click Storage and Cache -> clear. I don’t reinstall it before opening.

Hmm that should do it, sorry I don’t know how you’re still signed in after clearing storage. The user information and settings are storage that the device should be clearing.

Under App Data you should be able to clear storage.

Is it a specific instances modlog that is failing? I was testing with lemmy.ca and it seemed to be working. I’ll take a look at the other issues in the next release.

Hi, thank you for the report and this should now be resolved on version 398. To explain why this started happening I switched from trying to filter these out locally to sending the preference to the server so it does it and it’s a bit more performant on the client. Cheers!