Solved this, should be fixed in the next the release

Yes, the latest release of lemmy is 0.18.5

If it’s the account you are using rn, it is because, 0.19 is not supported yet by Jerboa

(It’s not fully released)

settings -> about -> crash log

post crash here/my dms/github

The thing is, I am using a third party library for those dialogs. They would be very interested in a minimum reproduction of the problem. So I wouldn’t have to invest to much time to fix it.

I see know what you mean with “left” and “right” screen. I thought it was a tablet first. Most likely it places the dialog in the wrong location.

But if I can’t reproduce this it’s gonna be hard to fix.

Does the more options work on the posts? Can you see the new design there?

I’ll see tonight if I can reproduce it somehow

Did it start when the dialogs of the corners changed? Did you ever see the new design?

Did it change since a update? and if so since which update?

Version, android version, device?

It is not related from upgrading from 0.48 to 0.49. (Very minor update that didn’t touch anything related)

Basically it is doing “checks” (instance online, JWT works, banned, etc) Looks like it got somehow stuck each time on a check. Which account(s) is this happening to?

You can get the logs but its a bit complicated. see https://github.com/dessalines/jerboa/issues/new?assignees=&labels=bug%2Ctriage&projects=&template=bug_report.yaml then How to get the full logs

Does a popup appear? like instance offline, etc, account banned, etc

Would it be possible that a moderator deleted your post between creating your post and saving your edit?

Do you have show read posts unchecked?

Discovered in July 2022, I joined in July 2023 where I then pushed the issue upstream

Yes, see https://issuetracker.google.com/issues/294102838

Ah yes, mb this was a bug introduced only recently, I have made a fix for it. It should land in the next update. https://github.com/dessalines/jerboa/pull/1260

Jerboa uses Jetpack Compose as toolkit instead traditional Views system that most apps use. The problem lays at core of a textfield component. It affects every app that uses this toolkit. And we can’t fix because it would need to be fixed at very low level, we don’t have access to nor domain knowledge about.

I don’t follow, after clicking on the community and going back the results are still there

np, see https://github.com/dessalines/jerboa/pull/1240

There is a fix for that one in review.