com.google.android.gms:play-services-ads:16.0.0 using old version com.android.support:customtabs

[Ashish Gupta]

Hi,

com.google.android.gms:play-services-ads:16.0.0 is using the old version com.android.support:customtabs:26.1.0.

The latest version is com.android.support:customtabs:28.0.0.

This results in the lint error:

"Error: All com.android.support libraries must use the exact same version specification (mixing versions can lead to runtime crashes). Found versions 28.0.0, 26.1.0. Examples include com.android.support:animated-vector-drawable:28.0.0 and com.android.support:customtabs:26.1.0 [GradleCompatible]"

Thanks

Ashish

[mobileadssdk-a...@google.com]

Hi Ashish,

Thank you for reaching out to us.

I'm afraid the Mobile Ads SDK has a dependency on version 26.1.0 of appcompat library which has a dependency on version 26.1.0 of the support library. We don't have any definite timelines on when this might change so I suggest that you keep an eye on our Release Notes for any future updates.

Regards,

Ivan Bautista

Mobile Ads SDK Team

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/129d7801-1647-45d7-b77d-002bed963877%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[shankar yadav]

Hi Ashish/Ads SDK Team

we are using 'com.google.firebase:firebase-ads:15.0.1' release in our app because we already used firebase SDK.  from last 7 days the match ratio is 2~3 % but today we got  40 % match ratio without any code changing. one more thing actually by mistake we put adUnitId instead of ADMOB_APP_ID in  MobileAds.initialize(this, "YOUR_ADMOB_APP_ID"). can you confirm me is this problem ??

On Wed, Oct 10, 2018 at 4:23 PM mobileadssdk-advisor+support via Google Mobile Ads SDK Developers <google-adm...@googlegroups.com> wrote:

Hi Ashish,

Thank you for reaching out to us.

I'm afraid the Mobile Ads SDK has a dependency on version 26.1.0 of appcompat library which has a dependency on version 26.1.0 of the support library. We don't have any definite timelines on when this might change so I suggest that you keep an eye on our Release Notes for any future updates.

Regards,

Ivan Bautista

Mobile Ads SDK Team

On 10/10/18 14:31:08 ash...@netflix.com wrote:

Hi,

com.google.android.gms:play-services-ads:16.0.0 is using the old version com.android.support:customtabs:26.1.0.

The latest version is com.android.support:customtabs:28.0.0.

This results in the lint error:

"Error: All com.android.support libraries must use the exact same version specification (mixing versions can lead to runtime crashes). Found versions 28.0.0, 26.1.0. Examples include com.android.support:animated-vector-drawable:28.0.0 and com.android.support:customtabs:26.1.0 [GradleCompatible]"

Thanks

Ashish

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
To post to this group, send email to google-adm...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/129d7801-1647-45d7-b77d-002bed963877%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
To post to this group, send email to google-adm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/18i7v0g000000000o74fvq0013t7hoz6kmjccpo6so30c1g68pjgd1h%40mail.gmail.com.

[mobileadssdk-a...@google.com]

Hi Shankar,

Your concern raised from this thread is different from the library version conflicts raised by Ashish in this thread. As you mentioned in that other thread, your ads were not loading before which explains the lower match ratio before, then yesterday, you confirmed that ads started loading again which explains the increase in your match ratio. 

On the other hand, if you put the incorrect value in the MobileAds.initialize(), then the pre-initialization of the SDK might not be successful. However, the loadAd() method will also initialize the SDK if it's not done yet. That said, if you have any further questions about the performance of your Ad Units (e.g. match rate), please use this troubleshooter instead. 

Regards,

Ivan Bautista

Mobile Ads SDK Team

On 10/10/18 23:13:56 shankar...@gmail.com wrote:

Hi Ashish/Ads SDK Team

we are using 'com.google.firebase:firebase-ads:15.0.1' release in our app because we already used firebase SDK.  from last 7 days the match ratio is 2~3 % but today we got  40 % match ratio without any code changing. one more thing actually by mistake we put adUnitId instead of ADMOB_APP_ID in  MobileAds.initialize(this, "YOUR_ADMOB_APP_ID"). can you confirm me is this problem ??

On Wed, Oct 10, 2018 at 4:23 PM mobileadssdk-advisor+support via Google Mobile Ads SDK Developers <google-admob-ads-sdk@googlegroups.com> wrote:

Hi Ashish,

Thank you for reaching out to us.

I'm afraid the Mobile Ads SDK has a dependency on version 26.1.0 of appcompat library which has a dependency on version 26.1.0 of the support library. We don't have any definite timelines on when this might change so I suggest that you keep an eye on our Release Notes for any future updates.

Regards,

Ivan Bautista

Mobile Ads SDK Team

On 10/10/18 14:31:08 ash...@netflix.com wrote:

Hi,

com.google.android.gms:play-services-ads:16.0.0 is using the old version com.android.support:customtabs:26.1.0.

The latest version is com.android.support:customtabs:28.0.0.

This results in the lint error:

"Error: All com.android.support libraries must use the exact same version specification (mixing versions can lead to runtime crashes). Found versions 28.0.0, 26.1.0. Examples include com.android.support:animated-vector-drawable:28.0.0 and com.android.support:customtabs:26.1.0 [GradleCompatible]"

Thanks

Ashish

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/129d7801-1647-45d7-b77d-002bed963877%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.

[shankar yadav]

Thank you for the clarification. 

On Thu, Oct 11, 2018 at 9:03 AM <mobileadssdk-a...@google.com> wrote:

Hi Shankar,

Your concern raised from this thread is different from the library version conflicts raised by Ashish in this thread. As you mentioned in that other thread, your ads were not loading before which explains the lower match ratio before, then yesterday, you confirmed that ads started loading again which explains the increase in your match ratio. 

On the other hand, if you put the incorrect value in the MobileAds.initialize(), then the pre-initialization of the SDK might not be successful. However, the loadAd() method will also initilaize the SDK if it's not done yet. That said, if you have any further questions about the performance of your Ad Units (e.g. match rate), please use this troubleshooter instead. 

Regards,

Ivan Bautista

Mobile Ads SDK Team

On 10/10/18 23:13:56 shankar...@gmail.com wrote:

Hi Ashish/Ads SDK Team

we are using 'com.google.firebase:firebase-ads:15.0.1' release in our app because we already used firebase SDK.  from last 7 days the match ratio is 2~3 % but today we got  40 % match ratio without any code changing. one more thing actually by mistake we put adUnitId instead of ADMOB_APP_ID in  MobileAds.initialize(this, "YOUR_ADMOB_APP_ID"). can you confirm me is this problem ??

On Wed, Oct 10, 2018 at 4:23 PM mobileadssdk-advisor+support via Google Mobile Ads SDK Developers <google-adm...@googlegroups.com> wrote:

Hi Ashish,

Thank you for reaching out to us.

I'm afraid the Mobile Ads SDK has a dependency on version 26.1.0 of appcompat library which has a dependency on version 26.1.0 of the support library. We don't have any definite timelines on when this might change so I suggest that you keep an eye on our Release Notes for any future updates.

Regards,

Ivan Bautista

Mobile Ads SDK Team

On 10/10/18 14:31:08 ash...@netflix.com wrote:

Hi,

com.google.android.gms:play-services-ads:16.0.0 is using the old version com.android.support:customtabs:26.1.0.

The latest version is com.android.support:customtabs:28.0.0.

This results in the lint error:

"Error: All com.android.support libraries must use the exact same version specification (mixing versions can lead to runtime crashes). Found versions 28.0.0, 26.1.0. Examples include com.android.support:animated-vector-drawable:28.0.0 and com.android.support:customtabs:26.1.0 [GradleCompatible]"

Thanks

Ashish

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
To post to this group, send email to google-adm...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/129d7801-1647-45d7-b77d-002bed963877%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
To post to this group, send email to google-adm...@googlegroups.com.

[secco.1...@gmail.com]

Hi Ashish

You can solve this compile error/warning directly in gradle. it's enough that you force the newest library at the place of the old one. Here is the code you shall insert in your app gradle file, You can add it below the repositories/dependencies part:

repositories {
    ...
}

dependencies {
    ...
}

configurations.all {
    resolutionStrategy {
        failOnVersionConflict()
        preferProjectModules()
        force 'com.android.support:customtabs:28.0.0'
    }
}

Let me know if it solved your issue

Best

Mac