this post was submitted on 08 Aug 2023
12 points (100.0% liked)

Voyager

5576 readers
14 users here now

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

Download on App Store

Download on Play Store

Use as a Web App

Download on F-Droid

Rules

  1. Be nice.
  2. lemmy.world instance policy

Sponsor development! 👇

Number of sponsors badge

💙

founded 1 year ago
MODERATORS
 

I tried browsing this community and using https://fedi-search.com/, but I can't find anything. Does anyone know if it can? If not, are there other applications that can?

all 8 comments
sorted by: hot top controversial new old
[–] morph@sopuli.xyz 3 points 1 year ago

It does on iOS.

[–] bdonvr@thelemmy.club 1 points 1 year ago

On iOS I can long press images and it gives a save option.

[–] DocF@feddit.de 0 points 1 year ago* (last edited 1 year ago) (1 children)

Works fine for me in Voyager. Long press the image, then select „Save to photos“.

[–] Jessica@discuss.tchncs.de 1 points 1 year ago

Hmm good to know thank you. I might need to update iOS or reinstall Voyager. I’ve kept it updated, but I never reinstalled when it changed its icon and I am on iOS 15.7. Long pressing on photos doesn’t do anything for me regardless of whether I am on the feed, in the post, or looking directly at the image.

[–] Jessica@discuss.tchncs.de 0 points 1 year ago (1 children)

@aeharding@lemmy.world would you happen to know if I am unable to view the contextual long press menu for saving images that @bdonvr@thelemmy.club shared because I am on iOS 15.7?

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

Should work on iOS. Can you try restarting the app and let me know if that works?

[–] Jessica@discuss.tchncs.de 1 points 1 year ago

I feel a bit silly now, but I did not try force closing the app or power cycling my phone. I was an Apollo user so I’m familiar with the long press contextual menu for saving to device, and I don’t recall it ever working on wefwef or Voyager on iOS 15.7.

I did however just go ahead and update to iOS 16.6 and it’s now working so I can’t say for certain if it was an OS requirement or just something that required a restart.