• About
• Dependencies
• Requirements
• Documentation
• Installation
• Usage
• Running the Sample app
• Running the sample backend
• Using the sample app
• Logging
• Errors
• Update factor's push token
• Delete a factor
• Clear local storage

Twilio Verify Push SDK helps you verify users by adding a low-friction, secure, cost-effective, "push verification" factor into your own mobile application. This fully managed API service allows you to seamlessly verify users in-app via a secure channel, without the risks, hassles or costs of One-Time Passcodes (OTPs). This project provides an SDK to implement Verify Push for your iOS app.

None

• iOS 10+
• Swift 5.2
• Xcode 12.x

SDK API docs

CocoaPods is a dependency manager for Cocoa projects. For usage and installation instructions, visit their website. To integrate TwilioVerify into your Xcode project using CocoaPods, specify it in your Podfile:

pod 'TwilioVerify', '~> 1.0.0'

Carthage is a decentralized dependency manager that builds your dependencies and provides you with binary frameworks. To integrate TwilioVerify into your Xcode project using Carthage, specify it in your Cartfile:

github "twilio/twilio-verify-ios" -> 1.0.0

Since version 1.0.0 of TwilioVerifySDK the prebuilt asset fat version .framework is been deprecated, to give space for the universal framework .xcframework. Make sure to use the new version of Carthage 0.38.0 that was release in order to support the xcframework assets, by using this version or a superior one, Carthage will download and unzip the TwilioVerifySDK.framework.zip attached in the release version, resulting in a TwilioVerifySDK.xcframework that can be found in the build folder of Carthage.

The Swift Package Manager is a tool for automating the distribution of Swift code and is integrated into the swift compiler. It is in early development, but TwilioVerify does support its use on iOS.

Once you have your Swift package set up, adding TwilioVerify as a dependency is as easy as adding it to the dependencies value of your Package.swift.

dependencies: [
    .package(url: "https://github.com/twilio/twilio-verify-ios.git", .upToNextMajor(from: "1.0.0"))
]

If you want to receive challenges as push notifications, you should register Your App with APNs. More info here

NOTE

The SDK should be used from a Swift class. See an example in the TwilioVerifyAdapter class

Since version 1.0.0, the target was changed from TwilioVerify to TwilioVerifySDK. Migrating from older versions will imply to update all the imports in your files, see an example in the TwilioVerifyAdapter class

See Verify Push Quickstart for a step-by-step guide to using this SDK in a basic Verify Push implementation.

• Clone the repo
• Change the Bundle Identifier to something unique so Apple’s push notification server can direct pushes to this app
• Enable push notifications
• Get the Access token generation URL from your backend (Running the Sample backend). You will use it for creating a factor
• Run the TwilioVerifyDemo project using Release as build configuration

• Clone this repo: https://github.com/twilio/verify-push-sample-backend
• Configure a Push Credential for the sample app, using the same APNs configuration
• Configure a Verify Service, using the Push Credential for the sample app
• Run the steps in the README file

• Press Create factor in the factor list (click on the +, top right)
• Enter the identity to use. This value should be an UUID that identifies the user to prevent PII information use
• Enter the Access token URL (Access token generation URL, including the path, e.g. https://yourapp.ngrok.io/accessTokens)
• Press Create factor
• Copy the factor Sid

• Go to Create Push Challenge page (/challenge path in your sample backend)
• Enter the identity you used in factor creation
• Enter the Factor Sid you added
• Enter a message. You will see the message in the push notification and in the challenge view
• Enter details to the challenge. You will see them in the challenge view. You can add more details using the Add more Details button
• Press Create challenge button
• You will receive a push notification showing the challenge message in your device.
• The app will show the challenge info below the factor information, in a Challenge section
• Approve or deny the challenge
• After the challenge is updated, you will see the challenge status in the backend's Create Push Challenge view

By default, logging is disabled. To enable it you can either set your own logging services by implementing LoggerService and calling addLoggingService (note that you can add as many logging services as you like) or enable the default logger service by calling enableDefaultLoggingService. Your multiple implementations and the default one can work at the same time, but you may just want to have it enabled during the development process, it's risky to have it turned on when releasing your app.

You may want to log only certain processes that are happening in the SDK, or you just want to log it all, for that the SDK allows you to set a log level.

• error: reports behaviors that shouldn't be happening.
• info: warns specific information of what is being done.
• debug: detailed information.
• networking: specific data for the networking work, such as request body, headers, response code, response body.
• all: error, info, debug and networking are enabled.

To start logging, enable the default logging service or/and pass your custom implementations

var builder = TwilioVerifyBuilder()
#if DEBUG
  builder = builder.enableDefaultLoggingService(withLevel: .all)
                   .addLoggingService(MyOwnLoggerService1())
                   .addLoggingService(MyOwnLoggerService2())
#endif
twilioVerify = try builder.build()

You can update the factor's push token in case it changed, calling the TwilioVerify.updateFactor method:

let updateFactorPayload = UpdatePushFactorPayload(sid: factorSid, pushToken: newPushToken)
twilioVerify.updateFactor(withPayload: payload, success: { factor in
  // Success
}) { error in
  // Error
}

See FactorListPresenter in the sample app. You should update the push token for all factors.

You can delete a factor calling the TwilioVerify.deleteFactor method:

twilioVerify.deleteFactor(withSid: factorSid, success: {
  // Success
}) { error in
  // Error
}

You can clear the local storage calling the TwilioVerify.clearLocalStorage method:

do {
  try twilioVerify.clearLocalStorage()
} catch {
  // Handle error
}

• Calling this method will not delete factors in Verify Push API, so you need to delete them from your backend to prevent invalid/deleted factors when getting factors for an identity.
• Since the Keychain is used for storage this method can fail if there is an error while doing the Keychain operation.