Connect for Lemmy App

2661 readers

9 users here now

A community for the mobile app Connect for Lemmy.

Links

founded 1 year ago

MODERATORS

[email protected]

Update broke Connect for me :( (self.lemmyconnect)

submitted 1 year ago* (last edited 1 year ago) by theNoob to c/[email protected]

21 comments fedilink hide all child comments

Updated the app this morning to 1.0.69 on a OnePlus Nord CE 5G running Oxygen OS 13. When it starts I get the splash-screen and it just stays there. Posting via LiftOff & Jerboa is still OK. Re-install no change

v1.0.72 fixed the issue

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

[–] [email protected] 9 points 1 year ago* (last edited 1 year ago) (2 children)

Thanks, publishing a hotfix now

Edit: should be rolling out once Google approves it. It's an issue with trying to migrate settings (before the migration path was just blow it away and start fresh) since I made a change there. Clearing app data or reinstalling will also fix it if you don't want to want for the hotfix.

Edit2: Should be live now

Edit3: just to keep all the info in one place, issue persists in 1.0.70 so I'm rolling back some of the Settings migration code. Hotfix 1.0.71 is in review with Google.

[–] automatonamaton 3 points 1 year ago (1 children)

Just updated to this new version (Pixel 7a) and same issue with hanging on splash screen. Thanks for being so responsive!!

[–] [email protected] 3 points 1 year ago (2 children)

Is it still hanging on 1.0.70?

[–] [email protected] 4 points 1 year ago* (last edited 1 year ago)

Same here, just updated but still only see the Connect logo on a black background :/ Edit: 1.0.71 fixed it, thanks for updating it so fast!

[–] automatonamaton 3 points 1 year ago (2 children)

Yessir

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

Ok thanks, going to rollback some of the migration code as it's better than being stuck at a splash screen. ETA ~30 mins.

Edit: Do you remember what version you were on before upgrading to 1.0.69? I suspect it's because I added code to handle the 1.0.68 -> 1.0.69 migration but not anything larger like from 1.0.65 which could explain why some people are unaffected.

[–] automatonamaton 1 points 1 year ago* (last edited 1 year ago)

I've updated each version you've released I believe, shouldn't have missed any last few days.

Latest release fixed the issue!

[–] [email protected] 1 points 1 year ago

1.0.71 should now be up, could you check if that's fixed the issue?