It’s been a while since the last release and there have been some changes. This release adds some general improvements to the app, fixes some bugs and adds some small features. See the full changelog (below) for details.
Full changelog
- Rewrite how actions are handled by the client. This enables some of the features below.
- Add new error state for comments that are unable to be sent/update that is viewable within the post itself.
- Add hide post as a quick action option.
- Add setting to show domain for links for the compact layout.
- Update dialog implementation. This should mean all dialogs should now support Material You.
- Update action details dialog.
- Improve how the app persists data. This should make crashing when returning back to the app less common.
- Update inbox so that messages are automatically marked as read on quick reply.
- Fix a bug where the downvote button would sometimes disappear.
- Fix the version name so it is v1.72.0
- Fix a bug where the bottom bar is showing when it’s not supposed to when viewing a post.
- Fix a bug where some screens have incorrect padding.
- Fix a bug where scroll to next/previous comment doesn’t work in certain edge cases.
- Fix a bug where some links are mistakenly treated as Lemmy links.
Update
I accidentally didn’t bump the minor version so will be doing another release, also made more improvements.
- Fix the version name so it is v1.72.0
- Fix a bug where the bottom bar is showing when it’s not supposed to when viewing a post.
- Improve how the app persists data. This should make crashing when returning back to the app less common.
Update 2
Minor change.
- Update inbox so that messages are automatically marked as read on quick reply.
Update 3
Bug fixes.
- Fix a bug where move to next comment will not work (used for the features relay navigation & volume rocker navigation).
- Fix a bug where going back to a post will not restore the scroll position.
- Fix a bug where certain system gestures will conflict with gestures in the app.
Update 4
More bug fixes. Will be released as v1.72.3.
- Fix a bug where some screens have incorrect padding.
- Fix a bug where scroll to next/previous comment doesn’t work in certain edge cases.
- Fix a bug where some links are mistakenly treated as Lemmy links.
Update 5
More bug fixes. Will be released as v1.72.4.
- Lock the side bar when the post screen is open or opening.
- Fix a bug where Fediverse links behave incorrectly.
- Fix a bug where some bottom sheets are not inset correctly.
Update 6
More bug fixes. Will be released as v1.72.5.
- Fix a bug where original images are not loaded when a thumbnail is tapped under certain circumstances.
- Fix a bug in the post screen. Previously if comments fail to load, the loading spinner will appear forever. This behavior has been changed so that an error message is displayed instead if comments fail to load.
- Fix a bug where the “restore settings” dialog will not show the list of setting backups.
- Fix a bug where a blank screen is shown is two posts are tapped at the same time.
- Improve error handling.
Update 7
Fix bullshit. Released as v1.72.6.
Update 8
Found a pretty bad bug that was introduced recently. Will push out a fix as v1.72.7.
- Fix retry logic on network calls not retrying properly and instead returning cached values.
The Android changelog doesn’t change.
Ah yeah. I should update those going forward.
Just to confirm what another user said here. Just got the notification this morning that the app updated, and now my PieFed account will no longer load anything. It works on desktop though. And this account and my old Lemmy Blåhaj account are working fine.
Can you test something for me? Can you switch to your piefed account in the app, then change the sort order to Hot or Active and let me know if that fixes the issue? Thank you.
I can’t reproduce this at all. Which instance & what error message are you seeing?
Alright I’m not sure if I missed a sneaky update in the mean time, but I suddenly had the thought to try clearing the cache in app info (after killing the app first), then try again. And now I’ve been successfully able to log in with my PieFed account and everything is loading again. I’m suggest to the other user to try the same.
My instance is piefed.blahaj.zone. I don’t get any particular error message, not like the other user. It just simply says this:

The result is the same in All or Local or the Summit community itself.
Also I just tried signing out and adding an account again and now this is what I get on the login screen:

So either way I can’t test switching between Hot or Active right now either.
I think I was able to track down the exact issue and will issue a fix soon. Thanks for surfacing this!
Fix bullshit. Released as v1.72.6.
Half my git commit messages look like this 😂
Can confirm that my bullshit has been fixed.
I’m still up to mine. Summit works great though!
This was a tiny change to remove the logic that blocks user interaction with the post list when the post screen is not fully hidden. It made the experience feel so clunky to me that I removed it out of frustration lmao.
Oh you don’t need to explain it! Thanks for the release btw, Summit has very quickly become my daily driver.
“Fix bullshit”
Best changelog ever.🤌🏼
Thank you so much for the app! I’ve tried almost all of them and this one is by far the one that suits my needs the most.
That said, I’m having trouble logging in with my piefed account (didn’t have any issues loggin in with my reddthat account). I get this message:

I had this same issue and just tried force killing the app in settings, then clearing the cache. After that, my PieFed account is now working again. Hopefully it helps you.
I signed up for an account on Piefed.zip account just to test this but I was unable to reproduce the issue. Can you verify that the issue is still happening? If so, can you think of any oddities with the settings of this account?
Fix a bug where the downvote button would sometimes disappear.
Yay!
Sorry for the delay. I actually fixed this oje before going on vacation but didnt make a release until now.
Youre a champion mate. We all appriceate your work.
My app just updated to 1.72.4 (298), and this bug seems to be still present.
That is so odd. I can no longer reproduce it at all. Do you have a consistent way to reproduce the bug?
Not that I’ve found so far, but I’ll try to pay attention. I do have it right now, though:

Just issued a new update. It fixes some general bugs. I’m not certain if it will fix the bug you’re seeing but there is a small chance it could.
Thank you for making what I think is the best and most feature rich Lemmy client.
For a couple of releases, navigating comments by using the volume button seems to have stopped working for me. I was going to report it earlier, but got away from it.
Is that something you’ve had any other reports about?
Will be fixed in the next release.
Amazeballs!
Amazeballs delivered! Comment navigation by volume button now works again.
Thank you @[email protected] (:
Dude you’re a machine! Not sure where you get the time, but thank you for all you do.
Thank you!
Thank you!
Summit is my favorite of the Lemmy clients, been using it for a while and probably will the entire time I use Lemmy - thanks so much!
Np. Glad you like it 😄
So now that you’re back, one thing I’ve noticed since the revamp of the inbox is that the little red number in a circle on the inbox indicating unread items is often very slow to update. Like, I will reply to my last unread message and the number is still there afterwards and I have to force refresh inbox and/or profile multiple times to make it go away. Not sure anyone else is experiencing this but it’s a bit of a minor nuisance.
Are you manually marking the inbox item as read? With the inbox update, the default behavior now is that the app will no longer auto-mark inbox items as read. You need to manually mark them yourself. You can change this behavior in settings though.
It mostly happens after directly replying using the quick reply button without first tapping Mark Read. I had auto-mark off. Testing now with it on.
EDIT: Same behaviour. Reply gets sent, comment does not get marked read. On refresh of the inbox the message is removed (because it’s been replied to) but the notification remains. Requires a couple of reloads to remove the notification icon.
Hmm. I can’t reproduce this issue locally. Generally the app will queue a update count update whenever something might cause it to change. It will take ~5 seconds for the update to complete. From my tests the unread count badge will update after ~5 seconds without having to do anything. I don’t have to do any manual refreshes.
You know, I’m impatient enough that I am probably starting to manually refresh before 5 seconds now that you mention it 😅
EDIT: Actually there is something - replying via the quick reply button doesn’t automatically mark read until refreshing the inbox. So if you quick reply the message is still in your inbox and the notification icon too, but both disappear on refresh (provided 5 seconds has passed). This seems like a bit of a halfway in-between behaviour between automatically marking read on reply and not?
Ah I see. I was testing on PieFed and PieFed doesn’t auto-mark messages as read when you reply however Lemmy does. I can add a feature that will auto-refresh your inbox on reply. This should fix the issue however there will still be that delay.
Aha! Yeah I am still on my regular old Lemmy account even though I did sign up for a couple of Piefed instances. That feature sounds excellent!
deleted by creator











