MultiScan Integration Troubleshooting Guide
Summary
Utilize this troubleshooting guide to help resolve issues you may face when integrating the MultiScan SDK.
SDK initialization issues
- Check if your token works by running the example code with your development token
- Check your token expiry on LastPass where token details have been shared
User authorisation issues
- Ensure User ID, salt and claims(optional) have been applied correctly. Learn how.
- Ensure User ID, salt and claims are consistent each time the same user is authorised
Cannot start Face or Body Scan
- First, check if setupMultiScanSDK() was called successfully
- Second, check if authorizeUser() was called successfully
- Third, check that areResourcesDownloaded() is true (resource have been downloaded entirely) - Resources applicable for BodyScan only
- Ensure input schema is followed correctly
- Ensure input values are within accepted ranges
SDK output issues
- Check if SDK output schema is followed correctly
- Check if values from JSON output are mapped and converted correctly
Scan credit error
- Ensure the correct user ID has been announced to ScanControl API prior to doing the scan
- Ensure a valid ScanControl product ID is used when calling the API
- If using DEV token, 'env:SANDBOX' should be called on the ScanControl API
- If using PROD token, 'env:PRODUCTION' should be called on the ScanControl API
Scan process instability
- Please check network speed or try switching to a different network
Error running release build from Android Studio or CLI
- There is a security mechanism that we have in place that prevents the use of debuggers in release mode. You should build the APK and install it directly on the device for testing