Voyager seems to have a bug that seemingly came with the new Voyager version: after posting a comment, screen space with rounded corners / camera notch are not fully utilized and black borders appear. This effect remains until app restart. App remains fully usable, just with a bit less screen space used.
Did a quick search of github issues but did not find this one reported.
Are others getting this?
Sorry for this low effort post instead of a real full bug report. I feel like this must be a known issue already but just didn’t find it.
Thanks for the great app!
You must log in or register to comment.
I’m getting it too, every time I post a comment or refresh the comments section.
Version 2.40.3
2.40.4 seemed to fix it for meEdit: and just after posting this comment i got it :(
For me the update worked well for two days and now is back.
Seems somehow random
Can you share a screenshot?
A comment was made here in this post where a helpful person posted an actual screenshot: https://lemmy.dbzer0.com/comment/22643454
Thanks again, great app!!!
Ah thanks. Are you running the app from the store? Also what version of voyager, and what phone model?
Pixel 9. GOS and using 2.40.4 updated today with Obtainium from github. I will see after posting this comment if the issue persists. Edit: did not get it from posting this comment! Seems fixed in todays release!
Thanks, let me know if it comes back. I’ve been trying to replicate on all my Android devices but no luck so far!
Just to reply off the back of this comment chain I am on a Pixel 6a running Graphene with the app acquired via aurora. It will happen every single time I go into composing a reply, even if I dont actually post a reply and back out of the compose. It doesnt happen when submitting a post however.
Unfortunately, it still exists after all. I got it now when posting another comment in this thread. So it doesn’t happen every time when posting it seems.
I am getting this all the time too.
What it should look like -
What it switches to -
Thanks for the screenshot!
No worries, I took them and came here to report the issue anyway so just jumped on the back of your post :)
deleted by creator
