Hey!
Thanks for reporting this. Could you also make a GitHub issue on this with some reproducible steps so that I can troubleshoot it? (e.g., the instance you're on, the link you tap on that causes the issue, etc.)
Hey!
Thanks for reporting this. Could you also make a GitHub issue on this with some reproducible steps so that I can troubleshoot it? (e.g., the instance you're on, the link you tap on that causes the issue, etc.)
Hey there!
This issue was noted and is already fixed in a nightly TestFlight build. See this GitHub issue for more details.
If you're not on the TestFlight build, there is still a workaround for this issue by setting Thunder to portrait mode temporarily. Doing this should bring back the back button on the top left!
Hey there!
Could you tell me what version of Thunder you're using and the instance you're using? Additionally, does this happen to all images or only a few images on the feed?
If it only happens to a few images on the feed, I would try to increase the time Thunder tries to determine the image dimension size. Here is a quick link to that setting: Thunder Setting: Debug > Feed > Image Dimension Timeout
Is there a way to finally contribute? I've got minimal coding expertise but would like to contribute in some way.
Of course! We're always looking for contributors to help with Thunder regardless of level of experience.
Here's some general information about Thunder
I believe this is expected behaviour! The comment itself was made from a different instance, but the original post was posted in the lemmy.world community.
Glad you figured out the issue!
I'll take a note here and see if there's a way to add some notification when this type of situation happens ๐
Does it work if you try to visit the comment from your instance? For example, this is the same comment but on lemmy.world: https://lemmy.world/comment/16079890
Hey! I just tried it myself as well on v0.7.0-1 and it seemed to have worked (navigated to the post and showed comments)
Incidentally, after submitting this post, I tapped the eyeball to view it and nothing happened.
This is a known issue and was fixed recently (but not yet released) See https://github.com/thunder-app/thunder/pull/1797!
Hey there, fellow Flutter dev! ๐
Thanks for tagging me in this and bringing this to my attention! I'll take a look at this issue on my end as well and apply some fixes to it.
Thank you! I'll definitely try to sprinkle a bit of new features here and there when I can, but the majority of my time will be spent on improving the core app stability and performance ๐
Hey!
If you're specifically talking about marking private messages as read, you'll have to use the latest nightly build (v0.7.0-1) in order to do it as it was just added recently.
If you're running v0.6.1, it won't be possible to mark an individual message as read unfortunately ๐