Perhaps it's issue #281?
It's fixed in the nightly builds. If it's a different problem, I think we need to open a separate ticket for it.
Perhaps it's issue #281?
It's fixed in the nightly builds. If it's a different problem, I think we need to open a separate ticket for it.
Yes, it is fixed in the nightly builds and will be included in the next release.
I had to rebuild this version with Java 17 instead of Java 11. Now it seems the build was successful, so it will be available on F-Droid soon 🥳
I'm glad you were able to fix this issue. I'm not sure what could have caused it, and I couldn't reproduce it. Perhaps some setting caused it?
I've created a new release (v0.2.1) to fix the issues in the F-Droid building process(functionally, it's the same as v0.2.0). Hopefully, this means the latest version will soon be available on F-Droid.
Did you manually re-login, or did Eternity tell you to do so? Just curious if I've missed anything 😅
It will take some time, unfortunately. The build has failed for some reason. I've observed this in my pipeline as well. I am still investigating the issue.
I think this issue is fixed in this release.
Yes, it's going to be updated very soon
Yes, I've released it as beta so that Google Play users can also try the new changes before the release. These builds are similar to the nightly, but I have to build them manually so they are updated less frequently.
I'm not sure what causes this issue. Does this happen when you click on a post, or does it happen when you are browsing for posts?
Also, what can you see on the web UI for these posts?
I've also experienced it for a long time now. I'm not exactly sure what causes this, but I'll try to look into it again.