TrueException
Handling error responses for cases of verifying non-Truecaller users
Last updated
Was this helpful?
Handling error responses for cases of verifying non-Truecaller users
Last updated
Was this helpful?
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()
4
"Desired permissions are missing"
When the requisite permissions are missing or not granted while making the verification request
6
“Sim state is not ready”
When the SIM state on the device is not ready
7
“Airplane mode is ON”
When the device is on airplane mode, hence causing missed call to not go through
2
"Phone number limit reached”
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
2
“Request id limit reached”
When the used device exceeds the maximum number of allowed verification attempts in a span of 24h
2
“Invalid partner credentials.”
When the partner key ( app key ) you have configured in your project is incorrect. Visit or basis the build in which you are facing the issue on
2
“Something went wrong: Failed to create installation.”
In case of Truecaller internal service error
2
“Invalid phone number”
When the input mobile number is not a valid mobile number
2
“Profile has not been created yet”
When 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 verifyMissedCall method or due to network issues