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
  • iOS SDK
    • What's New
    • How to test your app with the SDK
  • Android SDK
    • What's New
      • How to integrate the SDK in your application
      • How to verify the integration in your app with the SDK
      • Manual integration
      • Handle block responses from the server
      • How to retry requests that were blocked
      • Multiple AppIDs support
      • Hybrid App support
      • Enable support for Account Defender
      • Integration with React Native
      • Integration with Flutter
      • Integration with Ionic
      • Integration with gRPC
      • Migrating SDK from v2 to v3
    • How to test your app with the SDK
LogoLogo
Login
Login
HUMAN DashboardHUMAN WebsiteRequest a Demo
On this page
  • v3.0
  • Intro to the Doctor App
  • The Doctor App’s bundle
  • Enable the Doctor App
  • The Doctor App’s flow
Android SDKv3

How to verify the integration in your app with the SDK

Was this page helpful?
Previous

Manual integration

Next
Built with

v3.0

Intro to the Doctor App

The SDK comes with integration verification tool - “Doctor App”. The “Doctor App” 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, it will pop up as part of the app flow and will guide the developer on simulating a user flow to gather the required information for testing the integration.

The Doctor App’s bundle

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. In order minimize the SDK footprint, those assets are loaded dynamically in run time.
If you run the “Doctor App”, those assets will be loaded automatically (internet connection is required).

Enable the Doctor App

In order to enable this feature, set the PXPolicy/doctorCheckEnabled to true. Here is an example:

1policy.doctorCheckEnabled = true
Automatic retry feature won't work with the Doctor App

The Doctor App manipulates the SDK’s headers so requests will be blocked. However, this will make any retry request attempt to be blocked as well. In order to test the automatic retry feature, please use the testing tool via the portal.

Development only!

This feature is for development only and should not be shipped as enabled with the application to the store.

The Doctor App’s flow

  1. Welcome screen
    In this screen you select whether to start a new test or load the summary of a previous test, if one exists.

  2. Product selection screen
    In this screen you select which product to test:

    1. Bot Defender
    2. Account Defender.

  3. Instruction screen
    In this screen you get a detailed explanation on how to start a new test, what is expected to happen and what you can do in case you are not able to generate a challenge/captcha.

  4. Test selection screen
    In this screen you can select between two different types of tests:

    1. Native app framework - to test your native URL requests.
    2. Web view framework - to test your web view URL requests.
      When you are done executing a test, you will return to this screen to enable you to start the other test.

  5. Summary screen
    In this screen you review the test results. You can go into details regarding each test and get troubleshooting tips in case a test failed, to help you analyze what is causing this issue.

    Remember to switch the doctorCheckEnabled param false

    When you exit the “Doctor App”, your app is also terminated. Just remember to switch the doctorCheckEnabled param to false in case you finished validating your SDK integration. 6. When you exit the “Doctor App”, your app is also terminated.