Voyager

5663 readers

77 users here now

The official lemmy community for Voyager, an open source, mobile-first client for lemmy.

Rules

Be nice.
lemmy.world instance policy

Sponsor development! 👇

💙

founded 1 year ago

MODERATORS

aeharding@lemmy.world

aeharding@midwest.social

aeharding@vger.social

266

TestFlight for Voyager (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by aeharding@lemmy.world to c/voyagerapp@lemmy.world

105 comments fedilink hide all child comments

Test Flight is here!

https://testflight.apple.com/join/nWLw1MBM

It's appreciated testing various versions of iOS, and ensure all functionality matches the Progressive Web App.

Comment below with any issues that don't exist in the Progressive Web App and aren't listed below.

Known issues:

Post photo upload doesn't work
Haptics needed in many places
Saving a photo crashes

Thanks!

you are viewing a single comment's thread
view the rest of the comments

[–] Lord_Fluffington@lemmy.world 10 points 1 year ago (2 children)

I do find it interesting that the back swipe then scroll freeze issue isn’t entirely fixed. It doesn’t stay frozen like the PWA if you keep swiping but it still latches for a sec before you can keep swiping.

[–] alexius@lemmy.world 4 points 1 year ago (1 children)

Came to comment this. The back swipe then scroll freeze issue isn’t fixed at all to me. I can replicate the bug every time. The only two reasons for me to use this over the PWA for now are haptics and scroll to top. Hopefully this opens the door to push notifications in the future.

[–] fer0n@lemm.ee 2 points 1 year ago (1 children)

Push is already possible for Android PWAs and with iOS 17 also for iOS. Regarding the scroll freeze, does it still stay frozen for you as long as you’re trying to scroll after the back swipe?

[–] alexius@lemmy.world 1 points 1 year ago (1 children)

It does stay frozen until you lift the finger for a second or so. I see no difference whatsoever.

[–] fer0n@lemm.ee 1 points 1 year ago (1 children)

Hm, okay. For me that part is definitely fixed

[–] alexius@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (1 children)

I just noticed I’m an iOS version behind, so that may be it. I believe it was released this week. I’m on 16.5.1 instead of 16.6. Will edit this comment after updating to see if that does it.

Edit: Nothing changed.

[–] fer0n@lemm.ee 1 points 1 year ago

I wouldn’t be surprised if that doesn’t fix it, but sure, worth a shot :)

[–] fer0n@lemm.ee 2 points 1 year ago

Yes, that’s the same thing I was experiencing