If you're getting this on v314, it's due to the preload images setting being disabled. Tap on that link to go to the Settings page to turn that on. It's on by default and having it enabled is generally better.
I have it enabled but still get this issue sometimes (or a similar one)
The "solution" is to click on the URL in the lower left of the image. It seems like it's trying to load the webpage as an image file when I click the picture
I tried tapping on a bunch of images in active and top 6h but was not able to reproduce the image data error. You do need to close and reopen Connect after toggling for the preloading to take effect; and the errors to stop coming up.
If you've reopened the app and that error is still coming up, can you post a bug report? To do that, go into Settings and tap on the three dots in the top right. Then on Report bug. You can copy it and just reply here if you want. Mainly, I'm curious which settings you're using that seems to produce this problem.
If you're getting this on v314, it's due to the preload images setting being disabled. Tap on that link to go to the Settings page to turn that on. It's on by default and having it enabled is generally better.
Thanks! That seems to have fixed it. I turned that off based on this post but I don't know if it really helped with that issue.
I have it enabled but still get this issue sometimes (or a similar one)
The "solution" is to click on the URL in the lower left of the image. It seems like it's trying to load the webpage as an image file when I click the picture
I tried tapping on a bunch of images in active and top 6h but was not able to reproduce the image data error. You do need to close and reopen Connect after toggling for the preloading to take effect; and the errors to stop coming up.
If you've reopened the app and that error is still coming up, can you post a bug report? To do that, go into Settings and tap on the three dots in the top right. Then on Report bug. You can copy it and just reply here if you want. Mainly, I'm curious which settings you're using that seems to produce this problem.
I will next time I see it happen (so I can provide a URL) - I feel like it's certain domains in particular but I haven't verified