Error while using missed called functionality in two apps on the same device

[sumannewindia]

I am facing a peculiar issue and hence need your support to resolve it. We have two apps both using true caller missed call functionality. The issue is that when a user logs in to any app using missed called functionality, he is not able to authenticate himself in the other app immediately, installed on the same mobile device because truecaller API returns an exception. But the same works fine if uninstall one of the apps. Please let me know how to handle such scenarios because we have multiple apps and want to use true caller missed call functionality for authentication.

[singhalyogesh]

Hi sumannewindia The behaviour that you mention is expected. The SDK service is designed in this fashion to prevent system abuse due to malicious attempts. In case you are facing this issue while testing/QA phase, we would then request you to raise a ticket on our support portal here and we will whitelist your test numbers so that you don't face this issue.

For further questions, please feel free to visit our support channel for a faster and dedicated response : https://developer.truecaller.com/support

[sumannewindia]

Hi, Yogesh Singhal (@singhalyogesh) Thanks for the update. I do agree with the limit set to prevent system abuse, but here the use case is that if the true caller SDK successfully authenticates "missed call" verification initiated from an app (lets us name it as OLA), then the SDK returns an exception, when a "missed call" verification is initiated from another app (let's name it as UBER), installed in the same mobile device and using the same SIM (mobile no). Pls, note these two apps have different package names as well as SHA and true caller IDs. I believe the throttling rate limit should be based on the specific app/per device and not on the phone device in general. Also not sure if really this is already the case and if we have not implemented it properly (we will happy to share the code if required).

I have written to truecaller support, but there is no response for 2 weeks. Let me know if you have any idea how to resolve these, because we already have an app live with truecaller auth SDK integrated, and an upcoming app launch has been planned but we are unable to launch because of this issue.