[Deleted]

  • superfes@lemmy.worldEnglish
    1·
    23 days ago

    If you’re logged in on a computer you can deregister the device in your security settings and it will use the other available authentication types.

    I’ve always been able to select another way to verify my login.

    • throwawayacc0430@sh.itjust.worksOPEnglish
      0·
      23 days ago

      I’m just gonna copy paste what I said to another user on another thread regarding this topic:

      Okay, so I attempted to access it again. Its currently in a weird state of partial access.

      I can “log in” but as soon as I try to access anything, say, Gmail, I get that screen again.

      This is what the settings page looks like:

      So its not totally locked out, but its not functional either, I’m not even on a VPN.

      Notice, 2FA is off.

      Then I click Gmail and get this:

      I tap “more ways to verify” and get this:

      I tap the only option, and it circles back to the previous screen.

      • MrQuallzin@lemmy.worldEnglish
        1·
        23 days ago

        They said to try again on a computer. All your screen shots are from a phone. You might get the same result, but we won’t know until you attempt it.

        • Kairos@lemmy.todayEnglish
          01·
          23 days ago

          on a computer

          You mean a web browser? Those exist on mobile devices too.

          • MrQuallzin@lemmy.worldEnglish
            1·
            23 days ago

            A web browser is not a computer. A phone is not a desktop computer. Google (and most other large companies) keep many features restricted to their full websites, not mobile apps and mobile versions of their sites. For those who are used to/grew up with smartphones, tablets, and chromebooks, these tactics help to make it harder to leave their ecosystems as they aren’t used to navigating desktop environments.

            (Chromebooks do give desktop versions of websites by default, but they have helped reduce technological literacy in exchange for convenience)

  • dustyData@lemmy.worldEnglish
    1·
    23 days ago

    Just to be very clear. This is happening because you didn’t have MFA active. I know it hurts to hear, but this is why you always migrate first, wipe the device second. MFA would’ve allowed you several methods for proof of ID. If your phone gets stolen, then thieves can’t even use the phone for anything. You can remote wipe and block the device, and it turns into paperweight. The device nukes your data then locks the bootloader.

    • MicrowavedTea@infosec.pubEnglish
      1·
      23 days ago

      You should enable MFA yes. But it’s definitely not reasonable to expect a forced half-assed version of MFA that keeps changing when you DON’T enable MFA. OP should have migrated the account before wiping the phone but this behavior was not caused by them.

  • CosmicTurtle0@lemmy.dbzer0.comEnglish
    1·
    23 days ago

    I had this happen after I changed my unlock code and then locked myself out.

    I imagine part of this is a conflict between their logic for reinstalling your settings and the fact that your credentials have been changed and you need to unlock them. The account restore workflow doesn’t have a path for people who recently changed their passcode but need to log in.

    I ended up abandoning the process and starting over. But gave me the opportunity to try a new launcher.

  • Nyticus@kbin.melroy.org
    1·
    20 days ago

    I hate getting this when Google absolutely knows that I’m the one logging in and actively using said account!

    I get it, verification this and verification that, but for fuck sakes, it’s nothing but an obstacle course that drains seconds and minutes of doing.