[BUG] Sync Crashing after lemmy.world 0.19 update (lemmy.world)

submitted 8 months ago by cbarrick@lemmy.world to c/syncforlemmy@lemmy.world

12 comments fedilink hide all child comments

On my "subscribed" page, if I scroll down, the app crashes. Not sure of anything more than that. But it's definitely repeatable for me.

Device information

Sync version: v23.11.29-22:27    
Sync flavor: googlePlay    

View type: Smaller cards    

Device: ASUS_AI2302    
Model: asus ASUS_AI2302    
Android: 14

you are viewing a single comment's thread
view the rest of the comments

[-] dr_jekell@lemmy.world 5 points 8 months ago* (last edited 8 months ago)

This looks like it might be a corrupted database entry.

Trying to post a link to the image using the old.lemmy.world interface causes a problem as well

~~It looks like someone has posted a malformed image that is causing the issue.~~

[-] can@sh.itjust.works 6 points 8 months ago

It's this post

This crashes for me

[-] rdyoung@lemmy.world 6 points 8 months ago* (last edited 8 months ago)

It did something for me. Not exactly a crash but it refreshed back to the main page but a few posts away from this one.

Oh, now I see the image. That post was fucking with me too. Once I was able to hide that post the crashing stopped.

[-] can@sh.itjust.works 4 points 8 months ago* (last edited 8 months ago)

Not exactly a crash but it refreshed back to the main page but a few posts away from this one.

That's what happened to me. Repeated attempts to load it made a prompt to clear cache appear. I haven't had a full crash yet. Maybe there's other offending posts. This one is in thee communities though so it could hit a lot of people.

Edit: it's something to do with the user. They made another post in cryptography that breaks sync for me too.

They're on a different activitypub platform.

[-] cbarrick@lemmy.world 3 points 8 months ago

I'd be cautious.

These malformed images may be malicious.

A malformed image should not cause a crash. I'm not sure what libraries Sync uses for this stuff, but the bug should be reported upstream (assuming it's not just some exception mishandling going on in Sync.)