Bug: TrueCaller API "Verification Failed" — possible ClientSecret issue (potential FIX inside)

[mhtalha07]

Users of this library are consistently experiencing a "verification failed" error when attempting to log in via the Truecaller API. This appears to be a widespread issue preventing successful authentication.

Suspected Root Cause

It is hypothesized that the hardcoded clientsecret (lvc22mp3l1sfv6ujg83rd17btt) utilized by this library (and others like truecallerpy) may have been rate-limited or blacklisted by Truecaller's servers. Due to the public nature of this key and its widespread use, it has likely been flagged for anomalous activity, leading to failed verification attempts for all users.

Proposed Solution & Next Steps

The most likely solution is to use a new, unique clientsecret. It is possible that a new key can be obtained by registering for a Truecaller developer account.

If this is the case, a long-term fix for the library might involve:

• Investigating the official process for obtaining a developer clientsecret from Truecaller.
• Updating the library to require users to provide their own clientsecret during initialization, rather than relying on a single, hardcoded value.

This would prevent a single key from being disabled and affecting all users. We would appreciate it if other developers could investigate this possibility or confirm if using a new key resolves the authentication error.