This can happen if the server hangs on the page request. It should eventually either load or time out and show a message at the bottom to try again though.

This can happen if the image host doesn’t allow CORS. Is it happening on all posts with images or just some?

Powered paragliding

🤔 Please let me know if it comes back! And you can double check the version you’re running in the about app page.

I’ll kick off a release for this fix rn.

It’s not fixed in release yet, just beta.

Do you have remember community sort turned on or off?

I see what you’re saying, but I disagree it should be consistent: the user agent should accurately identify the software that’s requesting a resource.

When Voyager just sends VoyagerApp without the browser stuff, it’s because the code that is making the http request actually bypasses the browser entirely, and is done natively with CapacitorHttp (helps to bypass CORS for perf and server misconfiguration).

I could see an argument for changing it to CapacitorHttp/8.0 VoyagerApp/1.0 for API requests. But if voyager changed the header to include browser ua, that would actually be spoofing since the browser played no part of making or handling the request.

i’m not sure why this was causing issues here though, especially with the login, as that should just be 100% api stuff and therefore use VoyagerApp/1.0 from the native app?

Yes, that’s right, that is odd! 🤔

o you know if Voyager can send browser-like user agents when installed from App Store?

Voyager actually used to haha. But added a static voyagerapp user agent because lemmy.ml started blocking without last year 🫠 can’t win unfortunately. Thanks for fixing.

Btw, voyager PWA will always use browser ua, native app will use VoyagerApp/1.0 for api requests, AND <browser ua> VoyagerApp/1.0 for browser managed requests (like loading images).

TLDR native app will always have VoyagerApp/1.0 somewhere in the string, PWA doesn’t touch the ua

Thanks, can you check the test build and lmk if that fixes it?

Can confirm! I’ll try to fix next release

Edit: potential fix deploying to test build, I will release in a couple days assuming no regressions

Ah, that sounds like an old Lemmy glitch. I’m not sure what causes it. If you could do a screen recording I could confirm. Also you can check Lemmy-ui or other apps (with same account) to confirm.

Either is fine, GitHub is better for my tracking but /c/voyagerapp@lemmy.world gets more community support

Should be fixed in next release!

I think this is a Piefed bug, I’ve seen it before. I’m sure it’ll get tracked down at some point.

:(

Sorry I can’t be more help, but I’ll keep my eye out. Another thing you can try is backing up the app, then fresh reinstall and see if you can reproduce with stock settings. There may be a specific setting that causes it.

You can export/import app settings which should include tags. Does that not work?

If you can find the exact version that it started happening, and exact reproduction steps that would be helpful since I haven’t seen what you’re describing.

I haven’t been able to repro, works fine for me, android+piefed.zip+viewing ich_iel. Have you tried asking the feddit.org admins? Maybe you could send them your IP and they could investigate the logs. Its possible they are blocking the user agent/ip. Voyager should send “VoyagerApp” somewhere in the user agent for the native apps.

Thanks for letting me know. This will be fixed in the next release :)

Right? Jellyfin is awesome

Sorry, I fucked that up! Will fix ASAP

edit: Fix is in 2.38.0, building right now