Migrate to the Play Install Referrer API

I received message today from google play

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.```

**I am using (Firebase & AdMob ) in my project but i don't know what can i do because this libraries from google!**
1 Like

Update the Google libraries, as suggested?

I make update today and after that i received the email, but my question how can i know if my game used (install_referrer intent) or not ?

Are you using it? You would know if you coded it. Otherwise one of your assets may be. Did you try a Google search for “Firebase install_referrer intent”? It will tell you where to check (hint, Android manifest)

I don’t sure if i am using or not because this libraries automatic install when install asset in unity,
This my main Android manifest:

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android" xmlns:tools="http://schemas.android.com/tools" package="com.xxx.xx"
          android:versionCode="1" android:versionName="1.0">
  <application android:label="@string/app_name" android:icon="@drawable/app_icon">
    <!-- The MessagingUnityPlayerActivity is a class that extends
         UnityPlayerActivity to work around a known issue when receiving
         notification data payloads in the background. -->
    <activity android:name="com.google.firebase.MessagingUnityPlayerActivity"
              android:configChanges="fontScale|keyboard|keyboardHidden|locale|mnc|mcc|navigation|orientation|screenLayout|screenSize|smallestScreenSize|uiMode|touchscreen">
      <intent-filter>
        <action android:name="android.intent.action.MAIN" />
        <category android:name="android.intent.category.LAUNCHER" />
      </intent-filter>
      <meta-data android:name="unityplayer.UnityActivity" android:value="true" />
    </activity>
    <service android:name="com.google.firebase.messaging.MessageForwardingService" android:exported="false" />
    <meta-data android:name="com.google.android.gms.ads.AD_MANAGER_APP" android:value="true" />
    <meta-data android:name="com.google.android.gms.ads.APPLICATION_ID" android:value="xxxxxx" />
  </application>
</manifest>

Firebase manifest

<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2016 Google Inc. All Rights Reserved.

This file is placed in the Unity Android Plugin to make it support the
eclipse style directory structure. It's currently used only as a stub, and has
no real data that gets merged with the final manifest, but is none-the-less
needed for the plugin to be parsed correctly in the folder structure we use.
-->
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
          package="com.google.firebase.unity"
          android:versionCode="1"
          android:versionName="1.0">
  <uses-sdk android:minSdkVersion="14"/>
</manifest>

GoogleMobileAdsPlugin manifest

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.google.unity.ads" android:versionName="1.0" android:versionCode="1">
  <application>
    <uses-library android:required="false" android:name="org.apache.http.legacy" />
    <meta-data android:name="com.google.android.gms.ads.AD_MANAGER_APP" android:value="true" />
  </application>
</manifest>

AgoraAudioKit.plugin manifest

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
          package="io.agora.gaming.unity3d.wrapper"
          android:versionCode="1"
          android:versionName="1.0">

    <uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.RECORD_AUDIO" />
    <uses-permission android:name="android.permission.BLUETOOTH" />
    <uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS" />
    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
    <uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
    <uses-permission android:name="android.permission.WAKE_LOCK" />
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
    <uses-permission android:name="android.permission.READ_PHONE_STATE" />
    <uses-permission android:name="android.permission.READ_LOGS" />

</manifest>

I am sorry but i don’t know what is code for “install_referrer intent” and from where can i change !

I have got the same mail from Google Play and also looking for an answer.

I also received this email, not sure what to do now. The official AdMob plugin for Unity by Google does all those Play Services and other install stuff when imported to Unity. I found out it is something related to build Gradle in the stackoverflow link below but I am not sure what is build Gradle and how to update to play-services-ads 18.3.0 if Google don’t update their official AdMob plugin. Can someone please help me understand all this?

https://stackoverflow.com/questions/59276004/migrate-to-the-play-install-referrer-api-unity3d

I got the same email, and it seems I have three games having this issue. I’m not using AdMob, but I recently added Facebook SDK to these games. Maybe it’s related to that.

Looking into this too and found the Adjust SDK seems to pull in the INSTALL_REFERRER API.

<receiver android:name="com.adjust.sdk.ReferrerReceiver" android:exported="true" >
    <intent-filter>
        <action android:name="com.android.vending.INSTALL_REFERRER" />
    </intent-filter>
</receiver>

Seems to be in Firebase android - install_referrer intent deprecation - Stack Overflow

I don’t use firebase, I just use AdMob but still received this email.

I have a sense that it may be a false positive email from Google.

That might also be true. Let’s see, I think I will wait for some more days for the truth to come out.

I’m having the exact same issue, just using Admob and got this email. Please let me know if you find out something!

1 Like

facebook sdk is adding this permission. it is too note here that no admob and firbase sdk is been used in my project. i only have facebook sdk in my project with chartboost, applovin, unity iap, and unity ads integrated. I found this code in my manifest






Hope will get the solution soon!

I also wrote above that I only have the Facebook SDK.

Does everybody here with this issue have Facebook SDK?

I hope Facebook is aware of this, and they make a new SDK that could solve the issue:

1 Like

I don’t think it’s only Facebook, as others have mentioned, and I share your concerns.

1 Like

yahh that would be great if they update their sdk asap!
i am still stuck with the issue!

i guess its not only facebook then…! i suppose unity technologies will find a solution for it ASAP!

So I found the fix if you’re only using the official AdMob plugin by Google from the link below. The version 4.2.0 fixed it. They also released a newer version today which is 4.2.1 which I have not tried but it should also contain the fix. I made a build using 4.2.0 and the install referrer permission is no longer there and I submitted a build to Google Play.

1 Like