To start shielding your applications, you must create projects in the OneSpan Mobile Portal. A project contains the necessary elements to shield your application such as the app platform (Android or iOS), the platform-specific version of App Shielding you select, and configuration options you set.
To create a project
Sign in to the OneSpan Mobile Portal.
You are taken to the App Shielding Home page.

Click Create to create a new project for shielding your applications.
In the Create project side bar, specify the project details:
From the menu, select the platform of the application that you want to shield. With this, you select the version of App Shielding for the platform.
Start with the most recent App Shielding version. You can change a project’s App Shielding version afterwards, if necessary.
Specific versions of App Shielding and versions older than 12 months are archived to ensure you receive the latest security updates. All existing configurations can still be accessed and copied to newer versions.
Enter a project name.
(Optional) Enter a project description.
Click Create.
The OneSpan Mobile Portal creates the project and displays the Details page of your project with all relevant information.
Here you can do the following:
Change the App Shielding version to be used for shielding your application.
Download the App Shielding SDK package (including a configuration demo, relevant files, and samples).
View and edit any existing projects and/or configurations.
Generate a configuration key (after you created the configuration).

To edit your project, click on the three dots in the project’s Details page. You can change the project name and description, and you can change the App Shielding version you would like to use for the shielding process.

Create a project with a compatibility release of App Shielding
OneSpan also provides compatibility releases of App Shielding. These are distinguished from regular releases by the file name extension version number-SDKcompat.
A compatibility release is necessary if your app integrates a third-party SDK, e.g. a payment SDK, and this third-party SDK has its own debugger protection. In such a case, shielding with a regular App Shielding version is not successful as the debugger protection of the third-party SDK clashes with App Shielding. To ensure successful shielding of your app if you use a third-party SDK, you must use an App Shielding compatibility release.
A compatibility release should only be selected for integrations with third-party SDKs as using it impacts the overall performance. For integrations that do not use third-party SDKs or any other app feature whose debugger protection clashes with App Shielding, it is not necessary and not recommended to use the compatibility release.
Compatibility releases of App Shielding are never listed as “Latest”. To select a compatibility release for your project, follow these steps:
In the OneSpan Mobile Portal, create a new project for the required operating system with the latest App Shielding version.
Open the project you just created and click Change version.
From the list of available versions, select the compatibility release version.