Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
* The UNIX timestamp (in milliseconds) when this attempt was created.
* The name of the `VerificationCodeSender` used in this attempt.
* The message transport used in the failed attempt
* The type of client that initiated this attempt.
* Indicates the reason we selected particular sender. (e.g. 'adaptive', 'configured', 'lang_support', 'random')
Used in:
* The attempt was not sent due to suspected fraud
* The attempt was refused by the sender
* The attempt failed because the sender could not be reached or had an unexpected error
Used in:
* The UNIX timestamp (in milliseconds) when this attempt was created.
* The name of the `VerificationCodeSender` used in this attempt.
* An opaque collection of bytes provided by senders when an attempt is created and presented to senders when a caller checks a verification code. Verification code senders can use this space to store whatever state they may need to check a verification code (the code itself, for example, or an upstream session ID) after an attempt has been created.
* The UNIX timestamp (in milliseconds) at which this attempt will no longer be valid.
* A sender-specific identifier for this attempt. This may be an upstream session identifier, for example. The interpretation of this value will vary by sender. Senders that do not have remote session identifiers may leave this field blank. Remote session identifiers are not guaranteed to be unique.
* The type of client that initiated this attempt.
* Indicates the reason we selected particular sender. (e.g. 'adaptive', 'configured', 'lang_support', 'random')
* A registration session stores information about a current attempt to register a phone number. Registration sessions are created when a client first requests that a verification code be sent to a phone number and store all state related to the registration attempt including the phone number being registered, the VerificationCodeSender responsible for sending and verifying registration codes, and any persistent data that sender may need to verify codes.
* The E.164-formatted representation of the phone number being registered in this session.
* The successfully-verified code associated with this session. If this field is not blank, the remote client has successfully verified their registration. Callers may use this value to de-duplicate verification attempts (i.e. repeated submissions from a remote client due to an interrupted connection).
* A unique identifier for this session.
* The number of times a caller has attempted to check a verification code for the active registration attempt.
* The UNIX timestamp (in milliseconds) at which a caller last attempted to check a verification code for the active registration attempt.
* The UNIX timestamp (in milliseconds) after which this session will expire.
* The UNIX timestamp (in milliseconds) at which this session was created.
* A list of transports that have been rejected by senders when attempting to send verification codes in the scope of this session.
* A list of attempts that failed to send
Used in:
* Indicates whether an account already exists with the given e164 (i.e. this session represents a "re-registration" attempt).
* The MCC as reported by a number lookup service.
* The MNC as reported by a number lookup service.