New
- Support for Lemmy 0.19
- Lots and lots of refactoring cleaning up technical debt
- Added “Account settings” to replace “Lemmy Settings”
- This new section syncs up with your Lemmy account
- A few things will need updating such as your nsfw setting and sort
Changes
- Any action that fail now alerts the user via notification
- Show / hide NSFW has been moved to Settings > Account settings (this now respects your account choice)
- Sort has been moved to Settings > Account settings (this also now respects your account choice)
- Removed “mark posts as read” and “remember across devices” as Lemmy does this automatically
Github issues closed
- Tasker Integration: Action Configuration Broken & No Post Syncing #350
- User domain not shown in posts for accounts with a custom name #118
- Portrait 2 columns layout bug #11
- Unsubscribe action fails silently #151
- S4L doesn’t expose Bot account preferences #173
- Show NSFW content doesn’t sync with Hide NSFW Posts #170
- Show scores doesn’t sync with account setting #171
- Disabling “mark posts as read” does not work #356
- Show Read Posts not synced with Hide Read #174
- Default sort settings not shared with web app #163
- Show Profile Pictures doesn’t sync with Show Avatars #172
- S4L doesn’t pull/ignores web settings #70
- Crash when Biometric account lock is enabled #110
Other fixes
- Fixed a crash when searching within messages
- Fixed a crash in the in-built webview
- Fixed a crash when sharing posts
- Added a fix for HTML chars in the summarizer
Updates
- androidx.annotation:annotation > 1.7.0
- com.android.tools.build:gradle > 8.2.0-beta04
- com.google.gms:google-services > 4.4.0
- androidx.core:core-ktx > 1.12.0
You must log in or register to comment.
Holy shit! Welcome back!
Well that came out of left field
Lemmy 0.19 has a breaking change for it’s API. Can tell with the tech debt LJ has been sitting on this for a while waiting for that to go. This is definitely one of the longer release cycles for Lemmy
I had been expecting this.
Lemmy itself is still a work in progress and the new version apparently makes some major changes from the current version.
Sync is currently in a usable stable state so instead of squashing bugs in the current Sync version it was a better use of their dev time to work on a build for 0.19.
Great! Now we wait for lemmy 0.19 to go stable!
Since the update the app crash at startup. I’ve tried to delete the cache but it still doesn’t start.
try delete the data and start over again. something wrong with the previous config (when restored) that’s not compatible with the updated version.
Bleh, now when was my last backup…?
it depends on where you store it if you’ve made any backup before. You can check it by try to create a new backup, or a new restore. the app will point to some folder.
The app is now crashing on startup so I can’t even go into settings. I wonder if I could find the old apk online and install it?
try apkpure web, no malware found there as far as I know. Maybe you’ll need to install the apkpure app to install the apk. if that so, make sure you uninstall it once done.
apkmirror is also OK. Check there first before apkpure.
Do downgrades work that way? I’ve only tried updating installed app with apk files, never downgrading. I’ll report back if I try.
it may not work as the data may have been changed by the updated app. but, you’ll be fine if you’ve made some backup. You can just delete all the data/cache and restore from the backup data after that. If haven’t made any backup, there’s no guarantee until you try.
Worked with deleting data.but I had to relogin/reconfigure my accounts which I was trying to avoid.
yep. Unless you’ve have made some backup before, then you can use it if the dev fix the bug in the future. if. not., it would be such a hassle to reconfigure the setting again.
deleted by creator
deleted by creator
App crashes on launch after update for me repeatedly after it scanned my fingerprint. After a successful scan it sat on the main page with no content loading, and no buttons working for a half second or so before the crash.
Couldn’t get past it with a force close or a clear cache. I had to wipe the apps data which logged me out and reset my settings, and then I was able to log in again.
On a Samsing S22 Ultra running Android 13 OneUi 5.1
Did you have obscure usernames is account picker enabled?
My name was starred out in the left pull out menu so I believe so yes.
I think that’s what’s causing the crash. I made a bug report.
Edit: after some testing I’ve confirmed this
Interesting, i am not having issues.
Device information
Sync version: v23.11.29-22:27 Sync flavor: googlePlay Ultra user: true View type: Slides Push enabled: false Device: b0q Model: samsung SM-S908U Android: 13
Sort is broken now, trying to change it says “network error” and it defaults to “top 6 hours” which for many communities shows no posts.
Can’t revert to previous version of Sync for some reason, it prompts me to update it and refuses to start if I don’t.
The “Communities” button under the three dot menu still doesn’t do anything.
I can’t used previous settings. App will crash if I restore from backup. The only way I can use the updated app is by login and use default settings. Dev, please look into this. I don’t want to set the settings all over again.
Anyway, if you app crash, delete the data and cache, start over.
Did you have hide username in account picker enabled? If so there a bug with that.
Update: thanks. that’s really the bug. I manage to get it working. First, I uninstall the updated version and install the earlier version by using old apk (apkmirror). Then I restore backup. After that need to unhide the account picker, and make a new backup. Then, update the app to a new version and sign in, and restore with the backup. The new app will be good to go with the old setting (except the hide username option).
yes, I have. That could be it.
Could be leftovers from anti-piracy measures of reddit sync. I remember it was quite difficult to restore settings through titanium backup.
Based
Thank you for this <3
Welcome back! Thank you for the update.
Thanks for the update!
The app was crashing for me on startup like other people have described. I reset the data and as soon as I enabled “Hide username in account picker”, it started crashing on startup again.
So that’s the issue then? Has anyone reported this on the github issue tracker?
Doesn’t look like it. Go for it! (Sync doesn’t crash for me, or I’d take care of it)
Done! Do you have “Hide username in account picker” enabled? If not don’t try it. I wonder if I edited that out of my account backup would it work.
Hah, I do not have it enabled and will heed your warning. Thanks :-P Hope that’s a thing that gets addressed soon, for you guys!
I was able to load a post from my browser and disable the setting. All is working now. Hopefully an update gets pushed soon before more people give up and clear their data or move to another app.
Seems support for the ‘scaled’ sorting option is missing :(
Your instance isn’t updated to 0.19 yet (as it’s not finalized). Wait for the official release and for your instance to upgrade.
Hmmm I tried it with an anonymous account on lemmy.ml and it didn’t worked :(
Hm, that might just be an oversight then. Can anyone with a lemmy.ml account (or any other instances running release clients) confirm if scaled sort is available and working?
feddit.nl was updated to 0.19 over the weekend. Just checked to see if Scaled is now available.
Removed my account in Sync, and added it again. Scaled (and Controversial) seem to not be there. On the front page at least.
That’s disappointing. I guess the 0.19 support is half baked
Thanks for the update!
How can I get access to the beta?
I was able to sign up for it in Google Play, then I was able to update to the Beta after being accepted by going to the app page in Google Play.
Is there any way to hide the profile picture in the comments?
There is a toggle for it in account settings, but it doesn’t appear to stick. I toggled it off, but still saw profile pictures, and when revisiting the setting to copy the following link for you, I saw that it turned itself back on.
This setting is not getting saved properly. Even after saving it multiple time the settings just roll back to normal again.
Just reported this bug, thanks. I do wish I could disable them in sync only without disabling them in the webui too.
