Truecaller
Search…
2.6.0
Hello!
Why Truecaller SDK
Getting Started
ANDROID
Implementing user flow for your app
Scenarios for all user verifications : Truecaller and Non Truecaller Users
Generating App Key
Integrating with your App
Setup
App Key Configuration
Initialisation
Customisation
Implement Callbacks
Clearing SDK instance
Handling Error Scenarios
Verifying non Truecaller users
TrueException
Completing Verification
Advanced Steps
Server Side Response Validation
Instrumentation
Getting Release Ready
MOBILE WEBSITES
Implementing user flow for your Mobile Website
Generating App Key
Integrating with your mobile website
Getting Release Ready
IOS
Generating App Key
Integrating with your iOS App
Server Side Response Validation
FAQs
General
Developer Account
Android App SDK
Mobile Web SDK
Shopify Plugin
PRODUCT UPDATES
App Review Process
Introducing dark theme
Powered By GitBook
TrueException
Handling error responses for cases of verifying non-Truecaller users
While verifying your users using Truecaller's drop call flow, it might happen that the verification fails because of specific reasons. For these cases, the SDK will return to you the corresponding error message in the onRequestFailure() method in the VerificationCallback callback. You will receive the appropriate error message from TrueException using TrueException#getExceptionMessage()
  • When the used mobile number has exceeded the maximum number of allowed verification attempts within a span of 24 hours from the time the first verification attempt was made Error Message : " phone number limit reached"
  • When the used device exceeded the maximum number of allowed verification attempts Error Message : "request id limit reached"
  • When the partner key ( app key ) you have configured in your project is incorrect Error Message : "Invalid partner credentials."
  • When the input mobile number is not a valid mobile number Error Message : "invalid phone number"
  • In case of Truecaller internal service error Error Message : "Something went wrong: Failed to create installation."
  • In case the user has been successfully verified, but for some reason their profile is not created which could be due to incorrect profile data while creating TrueProfile() in verifyOtp() or verifyMissedCall methods or due to network issues.
    Error Message : "Profile has not been created yet"
Previous
Verifying non Truecaller users
Next
Completing Verification
Last modified 5mo ago
Copy link