Truecaller
Search…
2.7.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
Server Side Response Validation
Instrumentation
Getting Release Ready
Testing your verification flow
Google Play App Signing
Google Play Store app permissions declaration
Google Play Policy Change for Device Identifiers
Changelog
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
SHOPIFY APP
Generating App Key
App Configuration
Deactivating App Block
FAQs
General
Developer Account
Android App SDK
Mobile Web SDK
Shopify App
PRODUCT UPDATES
App Review Process
Introducing dark theme
Powered By GitBook
Google Play App Signing
In case you are using the app signing feature of google play store, when you upload your release build to the google play store, it assigns a new SHA1 fingerprint to your app - which might lead to UNAUTHORISED_PARTNER_KEY error for your app, since the appKey used by you in your app config was generated for a different SHA1, and hence won't work for the new SHA1.
In this scenario, you need to go to the "app integrity section" of the Google play console, where you would see 2 SHA1 keys (a) Upload Certificate SHA1 and (b) App Signing Certificate SHA1.
You need to note down the "App Signing Certificate SHA1" from the console, and generate a new Truecaller partner key ( app key ) for your play store build. Configure this key for your play store build in your project, and upload the build on play store for your users
Previous
Test Setup
Next
Google Play Store app permissions declaration
Last modified 1yr ago
Copy link