Class SubmitPhoneChallengeScreen

constructor

• new SubmitPhoneChallengeScreen(navigation: AndroidChallengeNavigation, challenge: EndpointChallenge, state: SubmitPhoneChallengeResponse): SubmitPhoneChallengeScreen

• Parameters

  • navigation: AndroidChallengeNavigation
  • challenge: EndpointChallenge
  • state: SubmitPhoneChallengeResponse

  Returns SubmitPhoneChallengeScreen

Readonlystate

submit

• submit(phone_number: string): Promise<
      | AddBirthdayChallengeResponse
      | DeltaAcknowledgeApprovedChallengeResponse
      | DeltaLoginReviewChallengeResponse
      | EscalationChallengeResponse.Root
      | ReviewContactPointChangeChallengeResponse
      | SelectContactPointRecoveryChallengeResponse
      | SelectVerifyMethodChallengeResponse
      | SetNewPasswordChallengeResponse
      | SubmitPhoneChallengeResponse
      | UfacWwwBloksChallengeResponse
      | VerifyCodeChallengeResponse
      | VerifyEmailChallengeResponse
      | VerifyEmailCodeChallengeResponse
      | VerifySmsCodeChallengeResponse
      | VoidChallengeResponse
      | ScrapingWarningChallengeResponse
      | ChallengeRequiredResponse
      | {
          error: string;
          message: string;
          status: string;
          get response(): string;
      }
      | {
          error?: undefined;
          message?: undefined;
          status: string;
          get response(): string;
      }>

• Parameters

  • phone_number: string

    I noticed that instagram app can send the same parameter in two different formats. e.g. CO +573153170682 and 573153170682 returns the same result. I'm not sure what affects the app to choose a format, but i can say that server can handle both.

  Returns Promise<
      | AddBirthdayChallengeResponse
      | DeltaAcknowledgeApprovedChallengeResponse
      | DeltaLoginReviewChallengeResponse
      | EscalationChallengeResponse.Root
      | ReviewContactPointChangeChallengeResponse
      | SelectContactPointRecoveryChallengeResponse
      | SelectVerifyMethodChallengeResponse
      | SetNewPasswordChallengeResponse
      | SubmitPhoneChallengeResponse
      | UfacWwwBloksChallengeResponse
      | VerifyCodeChallengeResponse
      | VerifyEmailChallengeResponse
      | VerifyEmailCodeChallengeResponse
      | VerifySmsCodeChallengeResponse
      | VoidChallengeResponse
      | ScrapingWarningChallengeResponse
      | ChallengeRequiredResponse
      | {
          error: string;
          message: string;
          status: string;
          get response(): string;
      }
      | {
          error?: undefined;
          message?: undefined;
          status: string;
          get response(): string;
      }>