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.
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.
The go.getvoyager.app links work well for those that doesn't have the app installed, so good for sharing with friends. Not really relevant for your use case though!
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.
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.
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)
Should be fixed in next release!