Unable to get provider com.google.android.gms.ads.MobileAdsInitProvider: java.lang.IllegalStateException

Question

I update my Android Studio (3.2.1) and its sdk to the latest version. After that it required a manual update for Manifest by adding these tags:

<application
    android:allowBackup="true"
    android:icon="@drawable/ic_launcher"
    android:label="@string/app_name"
    android:roundIcon="@drawable/ic_launcher"
    android:supportsRtl="true"
    android:theme="@style/AppTheme"
    tools:ignore="AllowBackup,GoogleAppIndexingWarning">

    <meta-data
        android:name="com.google.android.gms.ads.APP_ID"
        android:value="ca-app-pub-#############"/>

    <activity android:name=".MainActivity">
        <intent-filter>
            <action android:name="android.intent.action.MAIN" />

            <category android:name="android.intent.category.LAUNCHER" />
        </intent-filter>
    </activity>
    <activity android:name=".NewActivity" />
    <activity android:name=".PreviewActivity" />
    <activity android:name=".EditActivity" />
    <activity
        android:name=".preferencesdata.AboutActivity"
        android:theme="@style/Theme.AppCompat.DayNight.NoActionBar" />
    <activity android:name=".preferencesdata.SettingsActivity"
        android:label="@string/settings">
        <meta-data
            android:name="android.support.PARENT_ACTIVITY"
            android:value=".MainActivity"/>
    </activity>
</application>

whereby instead the app ID I put the real id of my app. The value has also been changed to the right Ad Unit id as shown here https://developers.google.com/admob/android/quick-start. I also called this function in the MainActivity.kt:

MobileAds.initialize(this, resources.getString(R.string.banner_ad_unit_id))

However, the problem could not be solved. It still prints as follows:

E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.easyapps.cryptnote, PID: 3991
    java.lang.RuntimeException: Unable to get provider com.google.android.gms.ads.MobileAdsInitProvider: java.lang.IllegalStateException: 

    ******************************************************************************
    * The Google Mobile Ads SDK was initialized incorrectly. AdMob publishers    *
    * should follow the instructions LINK to add a valid  *
    * App ID inside the AndroidManifest. Google Ad Manager publishers should     *
    * follow instructions here: LINK.                           *
    ******************************************************************************


        at android.app.ActivityThread.installProvider(ActivityThread.java:5156)
        at android.app.ActivityThread.installContentProviders(ActivityThread.java:4748)
        at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4688)
        at android.app.ActivityThread.-wrap1(ActivityThread.java)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1405)
        at android.os.Handler.dispatchMessage(Handler.java:102)
        at android.os.Looper.loop(Looper.java:148)
        at android.app.ActivityThread.main(ActivityThread.java:5417)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
     Caused by: java.lang.IllegalStateException: 

    ******************************************************************************
    * The Google Mobile Ads SDK was initialized incorrectly. AdMob publishers    *
    * should follow the instructions here: LINK to add a valid  *
    * App ID inside the AndroidManifest. Google Ad Manager publishers should     *
    * follow instructions here: LINK.                           *
    ******************************************************************************


        at com.google.android.gms.internal.ads.zzmn.attachInfo(Unknown Source)
        at com.google.android.gms.ads.MobileAdsInitProvider.attachInfo(Unknown Source)
        at android.app.ActivityThread.installProvider(ActivityThread.java:5153)
            ... 10 more

Could someone tel me why it does happen or help me to solve it? I tried to google the issue, but there are no solutions. It seems to be an a new still unsolved issue. Many thanks in advance.

I edited the question and added the manifest data. Now you should be able to see where I put the meta data tag. I am sorry, but I don't want to share app id and ads id, that's why I replaced or changed them. Thank for your help bro! — Mark Delphi, Oct 12 '18 at 21:34
Follow this answer https://stackoverflow.com/questions/53294162/cannot-import-com-google-android-gmsplay-services-ads17-1-1/53443104#53443104 — Tahmid Bin Rashid, Nov 23 '18 at 08:40
I am facing same problem, but in my app I didn't include ads, should I add the meta-data part? if so, where can I get the appID from? I didn't get where "Google addmob" could be found. — coder, Jan 07 '19 at 13:12
Please Note: metaData tag has to be handled separate ways depending what are you using to serve ads. When Using AdMod use: https://developers.google.com/admob/android/quick-start#update_your_androidmanifestxml When using Google Ad-Manager use: https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start#update_your_androidmanifestxml — SMagic, Jul 30 '20 at 11:31

Saveen · Answer 1 · 2018-12-28T06:24:28.387

74

This happened due to updated AdMob SDK. Now you need to add appID in your manifest file.

<application> . . . 
      <meta-data 
           android:name="com.google.android.gms.ads.APPLICATION_ID" 
           android:value="ca-app-pub-################~##########"/>
</application>

You can get appID from here -->Google addmob -->Select app --> App Settings --> App ID.

You can read more from here ads-developers.

If you want to use test ads before putting your own id check the AdMob test ids from here developers.google.

Hope this will help you. Thanks :)

edited Dec 28 '18 at 06:24

answered Oct 13 '18 at 16:37

Saveen

3,742
14
32
38

2

I found the problem, I used the wrong ID (ID for AdUnit) and that's why it did not work. Many thanks! – Mark Delphi Oct 13 '18 at 18:56
1

It worked for me, and just to add a side note, you may want to use test ads before putting your own id, where it says "ca-app-pub-################~##########" check the AdMob test ids at : https://developers.google.com/admob/android/test-ads – Herbert Schiller Dec 27 '18 at 18:03
@SaveenDhiman I am facing same problem, but in my app I didn't include ads, should I add the meta-data part? if so, where can I get the appID from? I didn't get where "Google addmob" could be found. – coder Jan 08 '19 at 06:39
1

Hi @coder Can i know which google service(com.google.android.gms:play-services) you are using in your application? – Saveen Jan 08 '19 at 10:58
1

@SaveenDhiman I just noticed I had com.google.android.gms:play-services-ads in my grade I commented it out and the error is not showing anymore, thank you. – coder Jan 09 '19 at 05:35

score 61 · Accepted Answer · answered Oct 26 '18 at 17:10

61

Google gave update for the Google ads so if you update your Admob library in gradle then you need to add this in your manifest.

<manifest>
   <application>
      <!-- TODO: Replace with your real AdMob app ID -->
      <meta-data
          android:name="com.google.android.gms.ads.APPLICATION_ID"
          android:value="ca-app-pub-################~##########"/>
  </application>
</manifest>

answered Oct 26 '18 at 17:10

Atif Mukhtiar

923
7
10

1

How can I avoid this if am testing using androidTests – vizsatiz Apr 03 '20 at 07:10
1

I've spent a lot of time finding right test AppId. Just add this official test id: _ca-app-pub-3940256099942544~3347511713_ [source](https://developers.google.com/admob/android/quick-start#update_your_androidmanifestxml) – Shpand Apr 16 '20 at 08:35
1

Also, be sure you are modifying "main\AndroidManifest.xml" and not "profile\AndroidManifest.xml" or "debug\AndroidManifest.xml" – J. Saw May 17 '20 at 16:43
The format of admob_app_id is changed like as mentioned in the android:value answer. – Ravi Yadav Aug 11 '20 at 12:34

score 29 · Answer 3 · edited May 14 '20 at 12:34

29

Add In Your Manifest File

<meta-data
            android:name="com.google.android.gms.ads.AD_MANAGER_APP"
            android:value="true" />

edited May 14 '20 at 12:34

IntelliJ Amiya

70,230
14
154
181

answered Dec 29 '18 at 05:02

Vivek Hirpara

671
5
16

why do add this? – MBH Jul 15 '20 at 08:36

score 8 · Answer 4 · answered Nov 24 '20 at 14:00

Don't get confused with APPLICATION_ID. You should not replace it with your application ID for ex. com.example.myapp. Just keep it as it is.

<application>
...
      <meta-data 
           android:name="com.google.android.gms.ads.APPLICATION_ID" 
           android:value="ca-app-pub-################~##########"/>
...
</application>

score 6 · Answer 5 · answered Oct 16 '19 at 18:31

Important: This step is required as of Google Mobile Ads SDK version 17.0.0. Failure to add this tag results in a crash with the message: The Google Mobile Ads SDK was initialized incorrectly.

<manifest>
    <application>
        <!-- Sample AdMob App ID: ca-app-pub-3940256099942544~3347511713 -->
        <meta-data
            android:name="com.google.android.gms.ads.APPLICATION_ID"
            android:value="ca-app-pub-xxxxxxxxxxxxxxxx~yyyyyyyyyy"/>
    </application>
</manifest>

score 4 · Answer 6 · answered Apr 07 '19 at 11:37

Google Mobile Ads SDK v17.0.0 for Android has just been released, and it comes with these important changes.

Required AndroidManifest.xml changes

Starting in version 17.0.0, if you are an AdMob publisher you are now required to add your AdMob app ID in your AndroidManifest.xml file. Once you find your AdMob app ID in the AdMob UI, add it to your manifest adding the following tag:

<manifest>
    <application>
        <!-- TODO: Replace with your real AdMob app ID -->
        <meta-data
            android:name="com.google.android.gms.ads.APPLICATION_ID"
            android:value="ca-app-pub-################~##########"/>
    </application>
</manifest>

Failure to add this tag will result in the app crashing at app launch with a message starting with The Google Mobile Ads SDK was initialized incorrectly.

What if I'm using Google Ad Manager instead of AdMob?

Publishers using Google Ad Manager will need to declare themselves as an Ad Manager app with a different tag to avoid the same crash:

<manifest>
    <application>
        <meta-data
            android:name="com.google.android.gms.ads.AD_MANAGER_APP"
            android:value="true"/>
    </application>
</manifest>

See the link for more details.

sureshraja0000 · Answer 7 · 2020-05-29T07:03:13.630

3

If you haven't published your app, try the following

 <meta-data
      android:name="com.google.android.gms.ads.AD_MANAGER_APP"
      android:value="true"/>

edited May 29 '20 at 07:03

answered May 29 '20 at 06:55

sureshraja0000

31
3

why do we add this ? – MBH Jul 15 '20 at 08:36
https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start#update_your_androidmanifestxml – SMagic Jul 30 '20 at 11:22

score 2 · Answer 8 · answered Oct 13 '18 at 13:09

2

I think the name should be "APPLICATION_ID" not "APP_ID"

answered Oct 13 '18 at 13:09

user1043409

33
6

1

Sure! In addition, I already tried to replace it with the real app id defined in build.gradle under applicationId. No success, the app still crashes.... – Mark Delphi Oct 13 '18 at 15:30
do you mean to replace "APPLICATION_ID" with which id? the App_id? because it crashes when i'm setting it this way. – eyalix Nov 20 '19 at 13:51

score 2 · Answer 9 · answered Sep 11 '20 at 12:49

With the new Admob library we have to initialize and load Ad in the onCreate() method and add the App ID inside AndroidManifest file like mentioned in the other answers. But don't put the Ad ID in AndroidManifest by confusing it with the App ID which was the mistake that I was doing.

Ex App ID:  ca-app-pub-xxxxxxxxxxxxxxxx~xxxxxxxxxx 

Ex Ad ID:   ca-app-pub-xxxxxxxxxxxxxxxx/xxxxxxxxxx

score 0 · Answer 10 · answered Aug 17 '19 at 18:49

In Unity3D starting V3.18 & Ad SDK V 7.45.0, you need to setup these data @ Menu : Assets > Google Mobile Ads > Settings & it will automatically write these data in manifest file.

Adding APPLICATION_ID & AD_MANAGER_APP into manifest file directly which is already given in other answers was still crashing for me.

score 0 · Answer 11 · answered Jan 14 '20 at 11:22

0

For those who are getting this error in Xamarin Forms Cross Platform app, the error

Unable to get provider com.google.android.gms.ads.MobileAdsInitProvider: java.lang.IllegalStateException`

it might be due to version of Xamarin.GooglePlayServices.Ads installed. When I used Version 71.1720.0 I was getting this error. Hence I uninstalled this version and restored it to Version 60.1142.1 and it worked without crashing.

For tutorial please refer to this Youtube Video

answered Jan 14 '20 at 11:22

Juned Khan Momin

2,028
10
30

1

Going back to an older version is not the real solution. According to some issues in the Xamarin.GooglePlayServices Github repo, a temporary workaround is to add the Xamarin.Android.ManifestMerger (preview as of 2020/15/01). – MSicc Jan 15 '20 at 13:33
I have exactly this issue with XF. @MSicc, could you give please more information, links? Thanks! – Zotyi Apr 03 '20 at 09:32

score 0 · Answer 12 · answered Feb 08 '20 at 13:34

java.lang.RuntimeException: Unable to get provider com.google.android.gms.ads.MobileAdsInitProvider: java.lang.ClassNotFoundException: Didn't find class "com.google.android.gms.ads.MobileAdsInitProvider"

If you are getting the error above and while searching you've come up here, it may not be because you forgot to insert adMob meta data inside your manifest. I have faced this issue and the solution is implementing the MultiDex inside your application.

Here is the Google instructions : link

score 0 · Answer 13 · answered Aug 11 '20 at 07:23

Make sure you check following steps.

1. Project level Gradle has google() added in all projects.

allprojects {
    repositories {
        google()
    }
}

2. App level Gradle has following dependency added mentioned same as sample below:

**implementation 'com.google.android.gms:play-services-ads:19.3.0'**

dependencies {
    implementation fileTree(dir: 'libs', include: ['*.jar'])
    implementation 'androidx.appcompat:appcompat:1.0.2'
    implementation 'com.google.android.gms:play-services-ads:19.3.0'
}

3. Update App-ID in AndroidManifest.xml mentioned in <meta-data>. Replace your App-ID in android:value

<manifest>
    <application>
        <!-- Sample AdMob App ID: ca-app-pub-3940256099942544~3347511713 -->
        <meta-data
            android:name="com.google.android.gms.ads.APPLICATION_ID"
            android:value="ca-app-pub-xxxxxxxxxxxxxxxx~yyyyyyyyyy"/>
    </application>
</manifest>

4. adView is added to the layout. Make sure you added ads:adUnitId not App-ID both are different.

I was getting error because I was confused between two. App-ID has "/" and adUnitId has "~". For testing purpose use "ca-app-pub-3940256099942544/6300978111" as adUnitId otherwise your account will get suspended.

When you are ready to publish you can add your real id and publish.

<com.google.android.gms.ads.AdView
      xmlns:ads="http://schemas.android.com/apk/res-auto"
      android:id="@+id/adView"
      android:layout_width="wrap_content"
      android:layout_height="wrap_content"
      android:layout_centerHorizontal="true"
      android:layout_alignParentBottom="true"
      ads:adSize="BANNER"
      ads:adUnitId="ca-app-pub-3940256099942544/6300978111">
  </com.google.android.gms.ads.AdView>

Check all 4 steps and you will be able to resolve this error.

Priyansh jain · Answer 14 · 2020-12-29T18:02:57.827

0

I have already added <meta-data...../> but the error didn't resolve. The solution is to put <meta-data.../> at last of other meta-data in your androidManifest.xml file present in android -> app -> src -> main . Like this:

<application>
   ...
   ...
   < meta-data 
        android:name="com.google.android.gms.ads.APPLICATION_ID" 
        android:value="ca-app-pub-################~##########"/> 
</application>

The solution is to put the meta data lines at Last (means below all other meta-data present in your android manifest file but just before closing application tag).

edited Dec 29 '20 at 18:02

answered Dec 06 '20 at 20:33

Priyansh jain

109
5

Worked for me after I had put in 4 hours into it. Really underrated answer. – Nandan Wewhare Dec 27 '20 at 11:52

Unable to get provider com.google.android.gms.ads.MobileAdsInitProvider: java.lang.IllegalStateException

14 Answers14

Linked

Related