On iOS. Currently on version 25.0, but I have been seeing this issue on the last several versions.
Sometimes when I load a feed, many images will partially load or not load at all. By partially load, I mean that some portion of the top of the image will load, but the rest will appear black.
When this happens, I cannot get the image to show in the app. Opening the post itself will show the partially loaded image. Refreshing the post will do the same. Going back and picking the feed again will still show the partial images.
If I view the post using the web link, the image usually loads immediately there.
It appears to me that the images become cached by the app and it will not attempt to retrieve the image again.
Do others experience this bug or am I the lucky winner?
Edit: here is a workaround that is working for me: Switch to another app then back to voyager. If your iPhone has no home button, just swipe right on the bottom bar to go to the previous app then swipe left to get back to voyager. This has been working for me and is super quick.
You must log in or register to comment.
I’ve had this exact issue many times already.
I have the same problem that happens somewhat randomly although O haven’t seen it for a while. I also created a post about the same thing and several people had some temporary workarounds: https://lemm.ee/post/1008156
I have a workaround.
- open the post
- click the chain icon to open the post in browser
- click to open the attached image
- close and go back
This seems to invalidate the cache for a couple of images from the same instance or something. Haven’t studied it in detail. But the problem returns after scrolling a bit.
I think I have a better workaround, which I stumbled on elsewhere (maybe reading the voyage issue log on gethub): Switch to another app then back to voyager. If your iPhone has no home button, just swipe right on the bottom bar to go to the previous app then swipe left to get back to voyager. This has been working for me and is super quick.
It happens to me as well from time to time. Force quitting seems to make it go away. Some times navigating around within the app makes it go away.
