For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
HUMAN DashboardHUMAN WebsiteRequest a Demo
Product GuidesEnforcer GuidesMobile SDKAPI ReferenceCustomer support
Product GuidesEnforcer GuidesMobile SDKAPI ReferenceCustomer support
    • Overview
  • Mobile SDK (for Android, iOS, and visionOS)
    • Android changelog
    • iOS, iPadOs, & visionOS changelog
    • Expo changelog
    • React Native Wrapper changelog
      • Testing practices
      • Integration Guide
      • How to upgrade from v3
        • How to Verify the SDK Integration in Your App
        • How to Test the SDK in Your App
  • iOS SDK
    • What's New
    • How to test your app with the SDK
  • Android SDK
    • What's New
    • How to test your app with the SDK
LogoLogo
Login
Login
HUMAN DashboardHUMAN WebsiteRequest a Demo
On this page
  • Bot Defender testing
Mobile SDK (for Android, iOS, and visionOS)v4Verify and Test

How to Test the SDK in Your App

Was this page helpful?
Previous

What's New

Next
Built with

Testing the SDK integration in your app is essential to ensure the best experience for your users.

Bot Defender testing

For Bot Defender, you should simulate challenges in various screens and scenarios in your app.

How to simulate a challenge

  1. Open the Testing tool in the portal.
  2. Select the “Testing (Native Mobile)” tab.
  3. Retrieve the VID of your device:
    • Using the VID Extractor
      1. Click on the “Find your VID” button.
      2. Enter your device’s public IP.
      3. Select the relevant session.
    • Using the SDK’s API
      1. Use the HumanSecurity/vid(forAppId:) function to get VID.
      2. Enter the value in the VID field.
  4. Insert the VID into the relevant field.
  5. Click on the “Start testing” button.
  6. In your app, trigger URL requests to your server. You should get a challenge. if not:
    • Move your app to the background
    • Bring it back to the foreground after few seconds.
    • Trigger URL requests to your server again.
  7. Solve (or cancel) the challenge and verify how your app behaves.