IGPAPI
    Preparing search index...

    Type Alias LoginTwoFactorResolution

    LoginTwoFactorResolution:
        | {
            kind: "approve_from_another_device";
            methodPicker?: LoginTwoFactorMethodPicker;
            pollQpl: TwoFactorBloksQpl;
        }
        | { kind: "choose_method" } & LoginTwoFactorMethodPicker

    How the shared flow resolved a two-factor answer, as a sum rather than a flat record: the approval screen's poll or the method picker's issued values — the two shapes the next screen can actually continue with. The approve variant carries the picker too when the caller asked for it up front; the choose variant always does, because that is the screen the answer leads to.

    Type Declaration

    • {
          kind: "approve_from_another_device";
          methodPicker?: LoginTwoFactorMethodPicker;
          pollQpl: TwoFactorBloksQpl;
      }
      • Readonlykind: "approve_from_another_device"

        The entrypoint scheduled the trusted-notification poll: the app waits for another device.

      • Optional ReadonlymethodPicker?: LoginTwoFactorMethodPicker

        The picker's values, when this caller fetched the picker up front.

      • ReadonlypollQpl: TwoFactorBloksQpl

        The has_been_allowed poll marker/instance the entrypoint issued.

    • { kind: "choose_method" } & LoginTwoFactorMethodPicker
      • Readonlykind: "choose_method"

        The entrypoint scheduled no approval poll: the app shows the method picker.