How to Verify the SDK Integration in Your App

Intro

The SDK comes with an integration verification tool - “Doctor App”. This is a tool that helps verify the SDK integration in your project by simulating a typical user flow in the application. When the “Doctor App” is enabled, a pop-up will appear as part of the app flow and guide the developer to simulate a user flow in order to gather the required information for testing the integration.

Android

The “Doctor App” includes assets that are used for the UI. Those assets are required only for the “Doctor App” usage and are not needed in your app production build. To minimize the SDK footprint, those assets are loaded dynamically at runtime.
If you run the “Doctor App,” those assets will be loaded automatically (internet connection is required).

iOS

The “Doctor App” includes assets that are used for the UI. Those assets are required only for the “Doctor App” usage and are not needed in your app production build. To minimize the SDK footprint, those assets are loaded dynamically at runtime. If you run the “Doctor App” on a real device with iOS 14 or above, those assets will be loaded automatically (internet connection is required). However, if you run the “Doctor App” on a simulator or on a real device with iOS 13 or earlier, you will need to add the HUMAN.bundle file to your project. It is important to remember to remove it from your project before you build and deploy your app to production.

You can get the HUMAN.bundle by running the following command in the Terminal (please refer to the relevant SDK version):

1
curl -LO https://jfrog.humansecurity.com/artifactory/files/doctor-app-assets/ios/2.1/HUMAN.bundle.zip

How to add the HUMAN.bundle file to your project

1. Download the HUMAN.bundle.zip file from the link above.
2. Unzip it and drag the HUMAN.bundle file to your project (make sure to link it to the relevant targets).

The Doctor App’s Flow

1. Start the SDK with the “Doctor App” enabled. You can enable it by setting the HSDoctorAppPolicy/enabled to be true when initiating the SDK.

   • Android:

1
import android.app.Application
2
import com.humansecurity.mobile_sdk.HumanSecurity
3
import com.humansecurity.mobile_sdk.main.policy.HSPolicy
4
5
class MainApplication: Application() {
6
7
    override fun onCreate() {
8
        super.onCreate()
9
        startHumanSDK()
10
    }
11
12
    private fun startHumanSDK() {
13
        try {
14
            val policy = HSPolicy()
15
            policy.doctorAppPolicy.enabled = true
16
17
            HumanSecurity.start(this, "<APP_ID>", policy)
18
        }
19
        catch (exception: Exception) {
20
            println("Exception: ${exception.message}")
21
        }
22
    }
23
}

• iOS/iPadOS/visionOS:

1
import HUMAN
2
3
class AppDelegate: UIResponder, UIApplicationDelegate {
4
5
    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
6
        startHumanSDK()
7
        return true
8
    }
9
10
    func startHumanSDK() {
11
        do {
12
            let policy = HSPolicy()
13
            policy.doctorAppPolicy.enabled = true
14
15
            try HumanSecurity.start(appId: "<APP_ID>", policy: policy)
16
        }
17
        catch {
18
            print("Error: \(error)")
19
        }
20
    }
21
}

2. Run your app. You should see the “Doctor App” UI displayed.

iOS/Android

3. Welcome Screen - Select whether to start a new test or load the summary of a previous test, if one exists.

4. Product Selection Screen - Select which product to test:

   1. Bot Defender
   2. Account Defender

5. Instruction Screen - Review detailed instructions on how to start a new test, what is expected, and steps to resolve issues.

6. Test Selection Screen - Choose between:

   1. Native app framework - to test native URL requests.
   2. Web view framework - to test web view URL requests.

7. Run the Test - Use your app according to the instructions.

8. Summary Screen - Review the test results. Explore detailed insights for each test and get troubleshooting tips for failed tests.

9. Export the test result to a JSON string from the summary screen. Share it with the support team if needed.

10. When you exit the “Doctor App,” your app is also terminated.

visionOS

1. Welcome screen - In this screen you select which product to test (Bot Defender or Account Defender) and which test to perform:

   1. Native app framework - to test native URL requests.
   2. Web view framework - to test web view URL requests.

   

2. Test screen - This screen shows the current step of the test in the main view, while the panel on the right provides a summary of the integration test results.

   

Note: Retrying blocked requests after the challenge is solved will not work while running the “Doctor App.” In this case, your request handler will receive a “challenge was solved” error.

Don’t forget to set HSDoctorAppPolicy/enabled to false when you finish validating the SDK integration.