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.
Update for users who downloaded the app from the Play Store: it looks like the app has been chosen for manual review. Usually when this happens it takes substantially longer to get the release approved by Google. I’ll update this comment/post once the release is reviewed.
Note: 1.44.4 has still not rolled out everywhere. I had to use the aurora store which allowed me to update.
I’ve rolled out the app to 100% early this morning. It’s possible there is some delay on Google’s end perhaps? It’s also possible the play store is caching the app page. In either case unfortunately I don’t think there is much more I can do here.
Thanks for adding support for custom emoji.
＼(￣▽￣)／
No problem. Unfortunately it looks like this release is stuck in review. It probably got selected to be manually reviewed by a real person or something.
Since the newest release, the app randomly crashes when I open comments. Sometimes it works, but in around 80% of cases it doesn’t. I don’t know what causes it.
Edit: And it even crashed after writing this comment, but luckily it did send it out.
Picture and text preview works fine, only when I open a post, it crashes.
I’m using a Oneplus 5 Android: 8.1.0 Omni-Version: 8.1.0
Yep I was able to reproduce the issue. Unfortunately the issue is only present in the release build and not debug builds so I did not catch it earlier. I am issuing an emergency release now.
Thanks for the quick patch! It works for me again.
Small bug report - navigating to the currently logged in profile screen, then attempting to go back, fails with the User & Settings overlay briefly flashing. The Up-button on this screen also appears to be connected to the wrong action, showing the drawer instead of navigating out of the profile screen as expected.
I don’t think I understand the exact steps to reproduce this. Could you please try to record a video of this issue or give step by step reproduction steps? Thank you!
- Press the profile icon in the top right corner (this opens the User & Settings overlay)
- Press your username (this opens the Profile Screen)
- Press the system back navigation button (I use gesture navigation fwiw)
- Expected behavior is to land back on the main screen, either with the User & Settings overlay visible or not)
- Actual behavior is the User & Settings overlay briefly flashing on top of the Profile Screen, with the user being left on the Profile Screen instead of navigating back to the Main Screen
- Press the Up-button in the top left corner
- Expected behavior is to land back on the Main Screen, either with the User & Settings overlay visible or not
- Actual behavior is that some kind of bottom sheet pops out from the side of the Profile Screen, with dismissing this sheet keeping the user on the Profile Screen (I thought this was the navigation drawer but it seems to be the navigation drawer content inside a bottom sheet?)
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!
Message sent, with video recording included (expires in 2 days)
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.
