B4A Library AdMob library

This library requires some configuration. Please see the tutorial: http://www.b4x.com/forum/basic4andr...-admob-tutorial-add-ads-your-application.html

Reference: Basic4android - AdMob

AdMob v2.00 - Based on Google Play Services. This version requires B4A v3.20.

AdMob v1.40 - Add support for SIZE_SMART_BANNER.
These ads will fill the whole available width: https://developers.google.com/mobile-ads-sdk/docs/admob/smart-banners

You can use the following code:

Adview1.Initialize2("Ad", "xxxxxxxx", AdView1.SIZE_SMART_BANNER)
Dim height As Int
If GetDeviceLayoutValues.ApproximateScreenSize < 6 Then
   'phones
   If 100%x > 100%y Then height = 32dip Else height = 50dip
Else
   'tablets
   height = 90dip
End If
Activity.AddView(AdView1, 0dip, 100%y - height, 100%x, height)

See this post for an additional requirement if using google play services v28: https://www.b4x.com/android/forum/threads/admob-library.7301/page-10#post-381519

 

[sorex]

This class is included in the latest version of android-support-v4.jar. Download it from Android SDK Manager and copy it to the additional libraries folder.

You need to add this line to the project:

#AdditionalJar: android-support-v4

I have some bizarre issue here.

On my test device I suddenly get a lot of crashes AFTER the (interstitial) ad has been loaded (it's not auto displaying)
It can't be trapped with TRY/CATCH either.


it seems to go away by adding that #addtionalJar line in the main module.

What is causing this and why didn't the crashes happen before during the last months?

Could it be that a specific type of pulled in ad requires more than the others?

 

[Erel]

I recommend you to switch to FirebaseAdMob and make sure to remove any usage of #ExcludeClass. It will fix such dependency issues.

 

[sorex]

ok I will have a look at it.

It's just that compilation without the exclude takes a lot longer.

 

[Erel]

It's just that compilation without the exclude takes a lot longer.

In B4A v6.0 it is no longer required when you compile with libraries that use the new format as only the required parts will be included.

 

[Davin]

anyone get this email ? and are the current lib need to updated too ?



Hi,
AdMob is committed to providing you the most effective monetization solutions. As we innovate, it’s important that we leverage the latest technologies to bolster our platform. As part of this movement, we are deprecating versions 6.4.1 and lower of the Android Google Mobile Ads SDK on September 15th, 2016.
In order to ensure that your ads continue to serve after September 15th, 2016, please upgrade to Google Mobile Ads SDK 7.0.0 or higher.

 

[AndrewKing]

I got this email too.

What should we do?

 

[Erel]

Switch to FirebaseAdMob: https://www.b4x.com/android/forum/t...b-ads-integrated-with-firebase-backend.67710/

It is based on the latest version of AdMob SDK.

 

[Computersmith64]

Switch to FirebaseAdMob: https://www.b4x.com/android/forum/t...b-ads-integrated-with-firebase-backend.67710/

It is based on the latest version of AdMob SDK.

Is that the only answer Erel? It appears that both the AdMob library & the mwAdmobInterstital2 library use Google Play Services for ads, so would they also be fine to use once the AdMob SDK v6.4.1 is deprecated? Does Google Play Services use the AdMob SDK, or is it completely separate?

 

[Erel]

The correct solution is to switch to FirebaseAdMob.

AdMob references Google-Play-Services.jar. Google has stopped updating this package.

 

[quique]

Hi Erel! Sorry to somewhat repeat the question / concern:

Is it necessary to perform all the integration steps on this new "firebase" platform ... like "2. Register with Firebase and create a new project: https://firebase.google.com/docs/ Make sure that the package name matches your app's package name." ?

This sounds like a ton of work, to replicate into each app, just to be compliant with the "new admob" requirements.

I am a bit appalled about this apparently mandatory "google twist" ...

Regards, Enrique.

 

[Pendrush]

Hi Erel! Sorry to somewhat repeat the question / concern:

Is it necessary to perform all the integration steps on this new "firebase" platform ... like "2. Register with Firebase and create a new project: https://firebase.google.com/docs/ Make sure that the package name matches your app's package name." ?

This sounds like a ton of work, to replicate into each app, just to be compliant with the "new admob" requirements.

I am a bit appalled about this apparently mandatory "google twist" ...

Regards, Enrique.

It's take you only few minutes to configure firebase project.

 

[quique]

It's take you only few minutes to configure firebase project.

... plus the code changes, plus compiling, plus testing .... multiplied by nn or even nnn apps.

 

[Computersmith64]

... plus the code changes, plus compiling, plus testing .... multiplied by nn or even nnn apps.

Yes - I'm also concerned about where this leaves those of us who use Google Play Services for leaderboards, achievements, etc... From my testing of a Firebase integration for ads yesterday, there appears to be a conflict between Firebase & the version of Google Play Services that I need to use for leaderboards & achievements & it doesn't appear that Firebase supports Google Play Games Services. I'm going to look into it more today & see if I can find a solution that doesn't require migrating all my apps to Android Studio. I'll comment on here once I know more.

- Colin.

 

[Davin]

if we dont update this thing. are we affected by the updates ? ( not getting any ads ) ?

 

[Erel]

I'm going to look into it more today & see if I can find a solution that doesn't require migrating all my apps to Android Studio.

I don't see how it will help. You will still need to update the SDK.

if we dont update this thing. are we affected by the updates ? ( not getting any ads ) ?

Based on Google mail, yes. Note that switching to FirebaseAdmob is very simple.

 

[Computersmith64]

I don't see how it will help. You will still need to update the SDK.

Well the problem is that B4A doesn't have any "native" support for Google Play Games Services & using Firebase for ads breaks the leaderboard & achievement functionality in my apps. Moving to Android Studio would enable me to implement AdMob & Google Play Games functionality without having to rely on 3rd party wrappers that get broken when Google makes a change to one of the libraries they use. B4A is a great development tool & it beats Android Studio hands-down when it comes to building layouts, but it also has a major shortcoming in that it doesn't support all of the Android functionality out-of-the-box. As I said in another post, I make my living from my apps - so I can't afford to suddenly find myself having to make a decision to either have zero revenue (because ads stop working), or remove a big chunk of functionality (because Google Play Games Services stops working) & negatively impact my user base. If I could find a solution that allows me to keep using B4A (& I'm still trying to see if I can modify the existing GPGS wrappers) then I'd happily keep using B4A, but if I can't then I'm not going to have any choice.

 

[Computersmith64]

As a follow-up to the Mobile Ads SDK v6.4.1 & earlier deprecation, a couple of points:

1) The deprecation date has now been pushed from September 16th to October 17th;
2) Any apps that use Google Play Services to serve ads will not be affected. It is only the stand-alone versions of the Mobile Ads SDK that will be deprecated.

So while it might ultimately be better to update to Firebase Ads, it's not absolutely necessary if you are using the versions of the SDK that are integrated into Google Play Services - which I think is the case with both the AdMob library (v2.0) & the mwAdmobInterstitial2 library. Too late for me though, as I have already updated to Firebase Ads...

 

[tpakis]

Thanks for the info! No need to hurry then.