---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/60406#article
headline: "60406: Initialization Error"
url: https://www.twilio.com/docs/api/errors/60406
inLanguage: en
dateModified: 2026-06-08T11:29:20.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 60406: Initialization Error

Log Type: APPLICATION

Log Level: ERROR

## Description

This error means your Verify integration tried to initialize a required SDK object or factor payload without all required values. Verify Push setup requires your app to create a `TwilioVerify` instance, obtain an Access Token from your backend, and provide the values needed to create a factor, including `identity` and the Verify Service SID.

### Possible causes

* Your app tried to initialize the Verify client without completing the SDK setup step that creates a `TwilioVerify` instance.
* Your backend did not return the Access Token, `identity`, or Verify Service SID that the mobile app needs before it can create a push factor.
* Your Access Token request omitted required values. Creating an Access Token requires the `serviceSid` path parameter plus `identity` and `factorType` in the request body.
* Your factor creation request or `PushFactorPayload` was missing one or more required values such as `friendlyName`, `factorType`, `binding.publicKey`, `config.appId`, `config.notificationPlatform`, `config.notificationToken`, or `config.sdkVersion`.
* Your app tried to use a `pushToken` before the device had a valid registration token, or passed an invalid `identity` value instead of an immutable non-PII identifier.

### Possible solutions

* Initialize the SDK exactly as shown for your platform before you create or verify any factors. For Android, create the client with `new TwilioVerify.Builder(applicationContext).build()`.
* Update your backend so it requests a Verify Push Access Token and returns the Access Token, `identity`, and Verify Service SID to the mobile app together.
* When you create an Access Token, include a valid Verify `serviceSid` and send both `identity` and `factorType: push` in the request. Use an immutable identifier such as a UUID, GUID, or SID for `identity`.
* When you create a push factor, supply every required value for the payload or API request, including the factor name, Verify Service SID, `identity`, Access Token, public key, app ID, notification platform, notification token, and SDK version.
* Validate that the device has a registration token before you pass it as `pushToken`. If you are not configuring push notifications for the factor, set `pushToken` to `null`.
* Retry the request only after you confirm that the missing values are present and correctly formatted. Unverified factors expire and become unverifiable after 1 to 24 hours, so recreate the factor if the original enrollment has already expired.

#### Additional resources

* [Verify Push & Silent Device Approval Overview](/docs/verify/push)
* [Access Token Resource](/docs/verify/api/access-token)
* [Factor Resource](/docs/verify/api/factor)