This topic answers common questions about integrating the Device Fraud Detection SDK.
What is the SDK size?
The SDK size varies by platform:
Android: A single-architecture SO file is approximately 3.4 MB. The AAR package includes SO files for three architectures and totals around 10 MB. After integration into an APK, only the SO file for the target architecture is packaged, resulting in an actual size increase of approximately 3.4 MB.
iOS: The single-architecture package is approximately 2.7 MB.
HarmonyOS: The package is approximately 3 MB.
To ensure anti-reverse-engineering capabilities and data security during network transmission, the SDK includes extensive code obfuscation, packing, and encryption operations, which contribute to the larger package size.
What is the validity period of a deviceToken? Can I reuse the same deviceToken for multiple server-side API calls?
A deviceToken is valid for 7 days and can be reused across multiple API calls.
Why must there be at least a 3-second interval between the initialization API and getDeviceToken?
The initialization API triggers an asynchronous initialization process that includes environment detection, fingerprint collection, and handshake communication with the server. This process typically takes about 3 seconds to complete. getDeviceToken depends on initialization being finished. If the interval is too short, data collection may not have completed, resulting in degraded token quality.
Which CPU architectures does the Device Fraud Detection SDK support?
Android: supports arm, armv7, and arm64 architectures.
HarmonyOS: supports arm64 architecture.
iOS: supports arm64 and x86_64 architectures.