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!

      • aehardingMEnglish
        2·
        18 days ago

        Ah thanks. Are you running the app from the store? Also what version of voyager, and what phone model?

        • passenger@sopuli.xyzOPEnglish
          1·
          18 days ago

          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!

          • aehardingMEnglish
            2·
            18 days ago

            Thanks, let me know if it comes back. I’ve been trying to replicate on all my Android devices but no luck so far!

            • passenger@sopuli.xyzOPEnglish
              1·
              18 days ago

              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.

            • theskyisfalling@lemmy.dbzer0.comEnglish
              1·
              15 days ago

              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.

                • theskyisfalling@lemmy.dbzer0.comEnglish
                  2·
                  10 days ago

                  Just as another update to this, the issue has definitely not been solved. It still happens but will never seem to do so when I am recording the screen.

                  I don’t know if the process of starting the screen recorder interrupts whatever is causing the issue but I have made a shit ton of recordings these last few days and it will never happen whilst recording but will still happen most times when a screen recorder is not activated.

                  • aehardingMEnglish
                    3·
                    9 days ago

                    Interesting… do you know how to try the beta? If I push a potential fix can you try to see if it fixes it with certainty after a couple days?

                • theskyisfalling@lemmy.dbzer0.comEnglish
                  2·
                  13 days ago

                  Heh.

                  So I have tried multiple times today and it isn’t happening any more for any replies I have made. It was consistently happening for quite a while and as soon as I try to record it stops. Fucking weird.

                  I will screen record for you if it start happening again but it seems to be fixed now?