AdMob Extension - open source now

The jetifier parameter is present and set to true for both arm-7 and arm-64

Which Defold version are you using?

Version 1.2.178

Please use the latest one - 1.2.181.

The error still comes up. Has it got something to do with auto migrating to AndroidX?

There should be a build log (log.txt) in PROJECTROOT/build/armv7-android/log.txt. Can you please share the log?

Here you go
log.txt (6.2 KB)

It looks like com.google.android.gms.ads.APPLICATION_ID is duplicated (defined in several places). Do you use custom AndroidManifest.xml?

Try to remove com.google.android.gms.ads.APPLICATION_ID section in custom manifests and provide your app_id only in game.project file by adding lines

[admob]
ios_app_id = ca-app-pub-***~***
android_app_id = ca-app-pub-***~***

Also ensure you add only one admob extension in project. I hope it will help.

3 Likes

I use the one from the builtins folder.

Ok, that’s good. But what about project dependencies? Can you share your list?

https://github.com/defold/extension-iap/archive/2.0.2.zip
https://github.com/defold/extension-review/archive/3.0.1.zip
https://github.com/defold/extension-gpgs/archive/2.2.0.zip
https://github.com/Lerg/extension-admob/archive/master.zip

Also if I may ask, why can’t we edit the AndroidManifest.xml file for native extensions?

Anything you add as a project dependency is read-only. Configuration is made either through code (functions exposed by the extension) or through new values added to game.project.

I did a test myself and was unable to build an APK since the AdMob extension uses Java 7 language features (switch statements for strings). We had support for Java 8 for a short period of time last beta while testing the dx to d8 migration but had to revert it due to some other issues. We will re-add it for the 1.2.182 release. Until then the AdMob extension by @sergey.lerg will not work.

1 Like

Thank you very much for your help.

That’s easy to fix, I wish I’d new Java 8 support is gone sooner. Will remove switch statements now.

Yes, sorry about that. It came and went sooner than we had hoped :slight_smile: But it’s back soon again, this time for good.

3 Likes

Just updated. Please try again.

1 Like

it worked!!! Thank you very much.

2 Likes