---
title: "Testing the completed Authenticator for iOS"
slug: "dpo-authenticator-sdk-for-ios-testing-the-completed-authenticator"
updated: 2026-10-27T20:13:12Z
published: 2026-10-27T20:13:12Z
canonical: "docs.onespan.com/dpo-authenticator-sdk-for-ios-testing-the-completed-authenticator"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.onespan.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Testing the completed Authenticator for iOS

## Using TutorialAppPlus

You can test your ASM implementation by building it as an iOS static framework and embedding it into TutorialAppPlus. For details on building and using TutorialAppPlus, see [Tutorial App for iOS](/dpoa/docs/s3suite94-tutorial-app-for-ios-1). The following section describes how to integrate the SampleASM into the Tutorial App. You will follow similar steps for your own ASM.

## Steps for Integrating SampleASM into TutorialAppPlus

1. Extract the asm_dev.zip and app_dev.zip files to a folder of your choice. We will refer to the extracted asm_dev folder as <ASM_SDK_HOME> and the extracted app_dev folder as <APP_SDK_HOME>.
2. Open <ASM_SDK_HOME>/SampleASM/SampleASM.xcodeproj in Xcode, specify the same target you used when building TutorialApp, and build SampleASM.
3. Using the Finder, copy the <ASM_SDK_HOME>/Frameworks/SampleASM.xcframework you just built to the <APP_SDK_HOME>/Frameworks folder.
4. Locate and open TutorialAppPlus/TutorialAppPlus.xcodeproj in Xcode.
5. In Xcode, go to **File** > **Add Files to “TutorialAppPlus”** and add <APP_SDK_HOME>/Frameworks/SampleASM.xcframework to the TutorialAppPlus project. **Note:** Adding SampleASM.xcframework also updates the Framework Search Path. To successfully build TutorialAppPlus, you must adjust the Framework Search Path entries located in **Build Settings** > **Search Paths** > **Framework Search Paths**.
6. Open the AppDelegate.swift file located in <APP_SDK_HOME>/TutorialAppPlus/TutorialAppPlus/
7. import SwiftSampleASM
8. Add SampleASM authenticator to ASM via following call in the didFinishLaunchingWithOptions function: SwiftSampleASM.addSampleAuthenticator()
9. Remove calls to add other authenticators. For TutorialAppPlus, remove these lines:

```plaintext
PresenceASM.addPresenceAuthenticator()
PresenceASM.addPresence8Authenticator()
SilentASM.addSilentShareableAuthenticator()
SilentASM.addSilentAuthenticator()
SilentASM.addSilent8Authenticator()
TouchIDASM.addTouchID8Authenticator()
PinASM.addPin8Authenticator()
TouchIDASM.addTouchIDNoLinkageAuthenticator()
PinASM.addPinAuthenticator()
TouchIDASM.addTouchIDWithPasscodeAuthenticator()
TouchIDASM.addPasscodeAuthenticator()
TouchIDASM.addTouchIDLinkageAuthenticator()
WatchASM.addAuthenticator()
```

1. In Xcode, click on the **General** tab. In the **Linked Frameworks and Libraries** section, click **+** and select SampleASM.xcframework inside the expanded entry for TutorialAppPlus, then click **Add**.
2. Build TutorialAppPlus/TutorialAppPlus.xcodeproj in Xcode.

## Creating XCFramework

In order to use your authenticator for both simulator and device, you need to create xcframework which includes all supported architectures.

Create xcframework with simulator and device architectures from the provided frameworks using the following commands:

```plaintext
xcodebuild -create-xcframework 
-framework "<path to simulator framework folder>/<ASM name>.framework" 
-framework "<path to device framework folder>/<framework name>.framework" 
-output "<path to xcframework folder>/<framework name>.xcframework"
```

## Update the Server with SampleASM Authenticator Metadata

You must also update your Server with the authenticator metadata corresponding to the SampleASM AAIDs. The .json authenticator metadata files are located in <ASM_SDK_HOME>/metadata. See [Add a New Authenticator](/dpoa/docs/s3suite94-add-a-new-authenticator-1).

## Using the FIDO Alliance Conformance Tool

Before your completed authenticator can achieve FIDO certification, you must test it using the conformance self-validation testing tool available through the FIDO Alliance website. As an authenticator implementer, you must register for a Vendor ID on a one-time-per-company basis. In addition, you must also register the metadata for each separate implementation of your authenticator. For more details on FIDO certification and conformance self-validation testing, see [https://fidoalliance.org/certification/conformance/](https://fidoalliance.org/certification/conformance/).