Ah, thanks for letting me know. I just checked and it’s because you’re running lemmy v0.19.3. That’s pretty old; I would recommend upgrading.

That being said, Voyager should have more helpful error messages for unsupported versions, and also should still support 0.19.3 until the next major release, so I’ll push a fix.

Thanks for checking!

I was actually testing an invalid login, where it says “connection error” instead of “invalid login credentials” because the backend error isn’t sent due to a CORS issue.

After attempting login with piefed.social vs feddit.online, here’s the screenshots. See the “CORS missing origin” error under trasnferred column for feddit.online. Also the lack of access-control-allow-* headers compared to piefed.social.

Awesome thanks for confirming!

That’s what happens when you try to signup, not login. There is a login button below pick a server button.

Also, try the web at https://vger.app/, probably easier to debug!

Do you know the admins? It looks like CORS is broken on signin (POST req), which causes the PWA to break.

Works for all the other instances so maybe they are doing something custom

The image link is broken, doesn’t work in the browser either

Thanks, I can reproduce it! It happens when the remember feature is enabled and you’re opening a post for the first time from a community where you haven’t opened any other posts from (since app startup)

I’ll fix in the next release

I could see there being a setting for that. It’s intentional by default for image posts to hide the body until tapping into the post, for example viewing photography communities you probably want to scroll through the images, and not have the feed cluttered with credits and descriptions and whatnot.

I tried but I can’t reproduce. Maybe there is some setting combination that is causing issues? I tested “remember community sort” comment toggle, but worked for both.

So odd! I’ve never experienced that before. Did you try restarting the phone? Also do you have offload unused apps enabled?

You found a bug in the beta; it’s a new issue!

Thanks for letting me know, I’ll investigate further this weekend. I can replicate; looks like it was due to a dependency upgrade.

Yeah, piefed thumbnails are pretty small. I don’t know if that’s a per server config or not though. Probably something to ask the piefed devs

Thanks! Try the next build ([697] d0aef95), it should fix these problems.

That’s the goal. Especially since the compat lib is separate, I’m hoping to get it mature enough to the point that it could eventually be community maintained.

Ah, it’s not you, piefed.ca is the main piefed instance people are having issues with. It looks like its just running a slightly outdated version of Piefed, hopefully fixed soon!

I think I saw that issue on first login. However it should go away on refresh/restart app, does that work?

piefed.ca is running slightly outdated version, hopefully that’s fixed soon :)

piefed.social should connect, that is what I used to test. Are you seeing issues with that instance?

Did you click this? You want to login, not join

💜

And happy 🍰 day!