You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have implemented the "WITH_OTP" flow. However, if the user wants to skip login, the bottom messgage stating "By proceeding, your phone number will be verified by Truecaller and you thereby accept to the Terms of Service".
As far as I've noticed, this comes on with the TruecallerSdk.getProfile call.
If the user proceeds with the authentication, it gets removed. Only in the case user skips/goes back, this message lingers around.
The text was updated successfully, but these errors were encountered:
Once the user decides to go via non truecaller flow, by either pressing back or CTA footer button or by initiating the flow as a non truecaller user that is when he/she would encounter this disclaimer on the bottom of the screen. This disclaimer is automatically dismissed once you pass the number entered by the user in the request verification method as you mention correctly.
This disclaimer is not optional to be displayed as this is a legal message shown by the SDK informing the user that going ahead their number would be verified by truecaller.
Now, coming to your query, if before passing the number user presses back then the dismissal of the disclaimer is on user's discretion.Therefore this cannot be hidden/removed explicitly.
Also, in case of any further technical/flow related questions, please feel free to reach us via our support channel https://developer.truecaller.com/support for a faster and dedicated response.
I have implemented the "WITH_OTP" flow. However, if the user wants to skip login, the bottom messgage stating "By proceeding, your phone number will be verified by Truecaller and you thereby accept to the Terms of Service".
As far as I've noticed, this comes on with the
TruecallerSdk.getProfile
call.If the user proceeds with the authentication, it gets removed. Only in the case user skips/goes back, this message lingers around.
The text was updated successfully, but these errors were encountered: