Hello Google Play Developer,
We recently announced that we’ll be deprecating the install_referrer intent broadcast mechanism. Because one or more of your apps uses this intent to track referrals, we wanted to ensure you make the switch before March 1, 2020. After this date, new versions of the Play Store app will no longer broadcast the install_referrer intent after app installs.
Action required
Migrate to the Play Install Referrer API to track your app installs for the following apps and/or games.
Any solution regarding this would be highly appreciated. Thanks in advance.
The Play Install Referrer API Client Library is written in the Java programming language and is a wrapper for the Android Interface Definition Language (AIDL) file that defines the interface to the Install Referrer service. You can use the Play Install Referrer API Client Library to simplify your development process.
The Google Play Referrer is a standard and highly reliable and accurate method to attribute conversions through Google Play (but not Android out of store). It enables the attribution provider to send attribution parameters to the store, which then passes them back to the source when the app is downloaded.
The Google Install Referrer is an Android-specific measurement technology that attributes clicks on Google Play Store app pages to the correlating app download. Google's Install Referrer framework sends an install referrer (or unique code string) to the Google Play store when an ad click has occurred.
If you are using firebase-core SDK for Firebase Analytics then remove it & exclue play-services measurement sdk.
As per Firebase SDK release notes:
No longer add the Android library com.google.firebase:firebase-core.
This SDK included the Firebase SDK for Google Analytics.
Now, to use Analytics (or any of the Firebase products that require or recommend the use of Analytics),
you need to explicitly add the Analytics dependency:
implementation ("com.google.firebase:firebase-analytics:17.2.1"){
exclude group: 'com.google.android.gms', module: 'play-services-measurement'
exclude group: 'com.google.android.gms', module: 'play-services-measurement-sdk'
exclude group: 'com.google.android.gms', module: 'play-services-measurement-impl'
}
This might solve your issue.
In my case, I found in my merged Manifest file usage of this source: "play-services-measurement:17.2.0", which includes permission BIND_GET_INSTALL_REFERRER_SERVICE, that was a cause of a problem. For fixing that, we can explicitly exclude deprecated modules, this fix works for me:
implementation ("com.google.firebase:firebase-core:17.2.0"){
exclude group: 'com.google.android.gms', module: 'play-services-measurement-api'
exclude group: 'com.google.android.gms', module: 'play-services-measurement'
exclude group: 'com.google.android.gms', module: 'play-services-measurement-sdk'
exclude group: 'com.google.android.gms', module: 'play-services-measurement-impl'
exclude group: 'com.google.android.gms', module: 'play-services-measurement-sdk-api'
exclude group: 'com.google.android.gms', module: 'play-services-measurement-base'
}
for testing you can check if permission BIND_GET_INSTALL_REFERRER_SERVICE still exists in your final merged Manifest file after gradle synchronization
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With