this post was submitted on 01 Nov 2024
21 points (100.0% liked)

Summit

741 readers
5 users here now

Community to discuss Summit, a Lemmy reader for Android.

App (Play Store): https://play.google.com/store/apps/details?id=com.idunnololz.summit

APK: https://github.com/idunnololz/summit-for-lemmy/releases

Patreon: https://patreon.com/SummitforLemmy

Ko-Fi: https://ko-fi.com/summitforlemmy

Website: https://summit.idunnololz.com/

founded 1 year ago
MODERATORS
 

First release since I've gotten back from vacation. This release addresses a good chunk of the user requests. There are some big ones left over that will be addressed in future releases.

Full changelog

  • Updated the UI for the emoji picker.
  • Updated the UI for deleted/removed posts so it has a distinct looked.
  • Added a new setting to disable markdown parsing for post titles.
  • Added a menu option to post/comments to copy it's contents.
  • Added a settings screen for the emoji picker, allowing users to modify or add emojis.
  • Added a setting to adjust the image size in the post feed.
  • Added a "Go to" dialog accessible in the main menu. This dialog allows you to jump to any Lemmy page directly given a link.
  • Added missing translations for Czech, German, Hindi, Italian, Swedish, and Turkish using Google Cloud Translations.
  • Cleaned up the settings for post/comment scores. Changed settings so that there is one setting for post scores and one for comment scores. There are three possible options for both settings: show scores (default), show up and down votes and hide scores.
  • Fixed a bug where the wrong icon is shown when viewing an instance's info.
  • Fixed a bug where the title is shown when it should be hidden on the community info/instance info screen.
  • Fixed a bug where spoiler tag state is reset if certain actions are performed. This also fixes a bug where spoiler tag state is reset when taking an advanced screenshot
  • Adjusted the width of the "include in screenshot" checkbox for advanced screenshots so it's easier to tap.

Update

Release has been in review for a few hours now. I hope it's not another 1 week review release :|.

Update 2

Found a bug introduced with this release. Sometimes tapping on a comment will not expand the comment actions. v1.44.1 will address this issue.

Update 3

Some more bug fixes:

  • Fixed a bug where spoiler tag state is reset if certain actions are performed. This also fixes a bug where spoiler tag state is reset when taking an advanced screenshot.

Update 4

  • Changed the logic for "mark post as read on scroll" to immediately mark any post that is fully scrolled off screen as read. The current logic can be a bit unpredictable about how far you'd need to scroll before a post is marked as read.

Update 5

I was made aware of a serious crash in the app in v1.44.2. I have addressed the issue and I am in the process of submitting an emergency release now (v1.44.3). Apologies for the inconvenience.

Update 6

Made a versioning mistake so the fix will be released as v1.44.4. The release has been submitted to the play store. It will be released as soon as it has been approved by Google.

Update 7

Release should be live.

you are viewing a single comment's thread
view the rest of the comments
[–] idunnololz@lemmy.world 2 points 6 days ago (1 children)

Thank you for the reproduction step. I attempted to reproduce this issue on 3 different devices but I was unable to. I ran these tests on the play store release (v1.44.4). It might be something specific to your app settings. If you'd like me to look into it further could you please send me (reply here or DM me) a dump of your app settings? You can generate this settings dump by going to Settings > Import & Export settings > Export settings > Copy to clipboard. Thanks!

[–] GissaMittJobb@lemmy.ml 2 points 6 days ago (2 children)

Message sent, with video recording included (expires in 2 days)

[–] idunnololz@lemmy.world 2 points 6 days ago

Looks like the issue is related to predictive back. I have a reproduction finally. I'll have a fix for it in the next update. One workaround seems to be to swipe really quickly (although not a great workaround). Or you can tap the up button.

[–] idunnololz@lemmy.world 1 points 6 days ago

Confirmed I received the information. I also saw the video. Unfortunately even with the settings I cannot reproduce the issue in the video. I have more test devices that I can test on. I can also look at the code to see if I can find any issues as well. In any case I think I have everything I need to look into this.