I can’t notice a pattern, but it happens all the time in both instances I use. I get to a post and there’s an image that can’t be loaded. I open the post on the browser and it loads fine.

(I’d share a screenshot of the browser but the inline picture upload feature is giving me grief now. ☹️)

Here’s the sample post: https://feddit.org/post/538582

In previous versions I could set the nsfw blur settings (Settings > Apperance > Blur NSFW) for my feed on a per account basis. This was good for having a nsfw and a sfw account that I could easily switch between. As of 2.12.4, it seems this setting is now global forcing me to have to switch it each time i switch accounts. This can also be problematic if i forget to re-enable the blur when switching back to my sfw account.

For some reason (I’m suspecting after an app update?), sometimes I open the Voyager iOS app and all of my settings have reset. I browse in compact, so I know right away something is off because the post images are huge. I did visit vger.app inside the app browser inside Voyager app, maybe that did it?

iOS app. Latest version (2.3.1).

When viewing a video from in a post if you swipe the playback position (attempting to skip forward), the app freaks out. It appears to be attempting to both interact with the video controls and swipe to the previous screen at the same time. At this point, both windows are active. The “back button no longer works. If I pick a different tab, nothing loads. I have to force close the app and reopen it.

In the screen recording, at 5s in I attempt to swipe on the video control. At that point most taps on the screen just move the split between the two windows. Moving the split fully does not resolve anything.

1. Tap search button on the bottom.

2. Search like normal for communities with the search term. Results returned like normal.

3. Clicking the unfilled heart (to subscribe) results in the error presented in the attached screenshot.

4. The back button (Android) doesn't work. App must be force-closed.

5. The subscribing action was successful; discovered on reboot.

6. Repeating the steps, but instead of the unfilled heart, clicking on the community successfully navigates to the community.

7. This didn't happen before.

8. I might be one update behind current as of Mar 18

I think this is a (minor) bug I noticed just now.

A post with the green megaphone from a sub that I subscribe to was showing up in All just now evening though I have the option turned on to hide subscribed in All/Local.

Specifically this is the post in question:

https://sopuli.xyz/post/10540905

Edit: on further thought, I'm not sure if the announcement part matters since I see other subs with that green megaphone in my Home feed and not in All. Sorry this is a terrible bug report.

I am on Android native app.

Haptic setting is set to off. The phone haptic is also off.

When I press and drag on the post menu the haptic is working.

Is it a bug 🐛 or intended feature?

Edit: fix liver (hepatic) to haptic 😂

Using Voyager 1.11.2 on iOS 16.6.1 I keep getting update notifications. When I choose to install the update, the notification goes away to soon come back again, yet the app version stays unchanged.

Sorry if my search skills where insufficient and this has been answered before.

Hello, with the recent NSO hack in the wild I thought I would give lockdown mode a try. Turns out wefwef/voyager doesn’t want to play nice for some reason. I am posting this from memmy app. Would you mind taking a look into the problem? Thank you!

Yesterday it was the Washington post. Today it's Sky news.

I'm on an iPhone 13 pro max, iOS 16.6 with the app "installed" on my home screen.

Edit: thanks for explaining everybody!

Mostly an issue on Android using Firefox, altho it's happened a few times using Brave as well

Sometimes it will work after multiple presses, sometimes not at all. It may be a Lemmy or Lemmy.world problem, but if it's Voyager I'm on Android using firefox

Basically title. After blocking a user, replies to comments still trigger inbox notifications.

It's not 100% consistent, but it seems to happen more when the images are partially off-screen.

Just wanted to note that when deselecting pure black (I always prefer something not so dark personally, so thank you for the option!!) the comments/post screen still uses pure black.

But the theme options are great! Appreciate it!

I can’t see a way to show the read posts again. Pressing the button a second time does nothing. V1.01.

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.

Example: I edit a post saying "Hello", i save it as "Hi" Then I open the edit menu again and it stills shows "Hello".

(The edit is saved in background but the app still has the old version loaded locally).

Scrolling through feeds gets stuck pretty often. Steps to reproduce this:

1. Scroll through feed, and click into a post
2. Scroll through the post, and use the left edge swipe gesture to go back to the feed
3. Scrolling is stuck

I have a workaround which is to nudge the home bar of iOS slightly upwards (but not completely go back to the iOS Home Screen), and then back down to re enter Voyager.

Would be awesome if this could be solved!

!