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

  • Kuro@lemmy.caM
    link
    fedilink
    arrow-up
    9
    ·
    edit-2
    1 year ago

    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@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

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

        • HungryKoala@feddit.de
          link
          fedilink
          arrow-up
          4
          ·
          edit-2
          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!

          • Kuro@lemmy.caM
            link
            fedilink
            arrow-up
            2
            ·
            edit-2
            1 year ago

            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@lemmy.world
              link
              fedilink
              arrow-up
              1
              ·
              edit-2
              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!

          • Kuro@lemmy.caM
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

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

    • RxBrad@lemmy.world
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      1 year ago

      Huh. Mine (Pixel 6a) updated to 69 (nice) six hours ago, and opened okay for me. I guess I’m just lucky.