New Admob SDK 20.x is deprecated

Post reply
6 favourites
From the Asset Store
20 game monsters
$8 USD
20 high-quality 2D monsters. This asset is perfect for a side scrolling game, or even a turn based RPG type game.
cruizRF's avatar
cruizRF

  • Please update sdk as soon as possible

  • For Android, i have this workaround to change project settings and gradle settings from 20.x to 23.2.x version manually.

    Subscribe to Construct videos now

    youtube.com/watch

    But i don't know how to do it for IOS yet.

  • In r401 the Mobile Advert plugin has now been updated. Internally it has switched over to using community-admob-plus-cordovayds@1.32.8 which now uses Google Mobile Ads SDK v23.2.0 for Android (and v11.3.0 for iOS). Hopefully this solves the immediate problem - let us know how it works out. We'll continue to review options for better long-term maintenance.

  • Hi, who has such a build error, don't worry, it's the latest version of FireBase plugin conflicts with AdMob.

    When building via cordova, you need to set the version manually (cordova plugin add cordova-plugin-firebase-analytics --variable ANDROID_FIREBASE_BOM_VERSION=“32.4.1”).

    Those who have no extraneous plugins should have no problems.

    _____

    Error: Checking Java JDK and Android SDK versions

    ANDROID_HOME=~~/androidSDK (recommended setting)

    ANDROID_SDK_ROOT=~~/androidSDK (DEPRECATED)

    Using Android SDK: ~~/androidSDK

    /> Task :wrapper

    BUILD SUCCESSFUL in 680ms

    1 actionable task: 1 executed

    Subproject Path: CordovaLib

    Subproject Path: app

    Library expects a BoM package: com.google.firebase:firebase-analytics

    /> Configure project :app

    Adding classpath: com.google.gms:google-services:4.4.0

    /> Task :app:preBuild UP-TO-DATE

    /> Task :app:preDebugBuild UP-TO-DATE

    /> Task :app:mergeDebugNativeDebugMetadata NO-SOURCE

    /> Task :app:generateDebugBuildConfig

    /> Task :CordovaLib:preBuild UP-TO-DATE

    /> Task :app:javaPreCompileDebug

    /> Task :CordovaLib:preDebugBuild UP-TO-DATE

    /> Task :CordovaLib:writeDebugAarMetadata

    /> Task :app:generateDebugResValues

    /> Task :app:checkDebugAarMetadata

    /> Task :app:processDebugGoogleServices

    /> Task :CordovaLib:generateDebugResValues

    /> Task :CordovaLib:generateDebugResources

    /> Task :CordovaLib:packageDebugResources

    /> Task :app:mapDebugSourceSetPaths

    /> Task :app:generateDebugResources

    /> Task :app:packageDebugResources

    /> Task :app:createDebugCompatibleScreenManifests

    /> Task :app:extractDeepLinksDebug

    /> Task :CordovaLib:extractDeepLinksDebug

    /> Task :app:parseDebugLocalResources

    /> Task :CordovaLib:processDebugManifest

    /> Task :CordovaLib:compileDebugLibraryResources

    /> Task :app:mergeDebugResources

    /> Task :app:processDebugMainManifest FAILED

    See https:/~~/manifest-merger for more information about the manifest merger.

    20 actionable tasks: 20 executed

    ~~/AndroidManifest.xml:92:13-59 Error:

    Attribute property#android.adservices.AD_SERVICES_CONFIGgwh@resource value=(@~~/gma_ad_services_config) from [com.google.android.gms:play-services-ads-lite:23.2.0] AndroidManifest.xml:92:13-59

    is also present at [com.google.android.gms:play-services-measurement-api:21.5.0] AndroidManifest.xml:32:13-58 value=(@~~/ga_ad_services_config).

    Suggestion: add 'tools:replace="android:resource"' to <property> element at AndroidManifest.xml to override.

    FAILURE: Build failed with an exception.

    * What went wrong:

    Execution failed for task ':app:processDebugMainManifest'.

    /> Manifest merger failed : Attribute property#android.adservices.AD_SERVICES_CONFIGgwh@resource value=(@~~/gma_ad_services_config) from [com.google.android.gms:play-services-ads-lite:23.2.0] AndroidManifest.xml:92:13-59

    is also present at [com.google.android.gms:play-services-measurement-api:21.5.0] AndroidManifest.xml:32:13-58 value=(@~~/ga_ad_services_config).

    Suggestion: add 'tools:replace="android:resource"' to <property> element at AndroidManifest.xml to override.

    * Try:

    /> Run with --stacktrace option to get the stack trace.

    /> Run with --info or --debug option to get more log output.

    /> Run with --scan to get full insights.

    /> Get more help at https:/~~/help.gradle.org.

    BUILD FAILED in 1s

    Command failed with exit code 1: ~~/gradlew cdvBuildDebug

  • anybody try the new beta R401 with updated mobile advert plugin?

  • anybody try the new beta R401 with updated mobile advert plugin?

    I've updated one app. So far so good, ads are running, I don't see any errors.

  • thanks for your contribute

  • Betas are risky but it seems there is no other solution at the moment. The last time I tried a beta I had problems with localstorage.

  • I have also updated, ads are running smoothly but google shows the same error as before the update.

  • I have also updated, ads are running smoothly but google shows the same error as before the update.

    It won't go away by itself, you need to archive it.

    Even though it has a red sign, it's just an important notice that says that you can no longer release updates with this version of the SDK.

  • Thanks you were right, many thanks for the hint!

  • Someone pointed out that Advanced Minification is causing problems and I was able to confirm this, still trying to figure out what the problem is with the new Cordova plugin we are using.

    If ads are not showing for anyone trying this out, try using Simple or None minification.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • Can confirm advanced minification is broken, but simple minification works.

    Also if adding firebase in android studio you have to change manifest.xml, and rebuild, because merge is broken.

    Search <property> in manifest and add

    tools:replace="android:resource"' to <property> element at AndroidManifest.xml to override.

    Can confirm this fix works.

  • I feel rather stupid asking, but I haven't used C3 in a dog's age.

    Any directions on how to actually fix whatever it is that Google wants done?

    Google seems a bit light on directions and though I somewhat remember how to add AdMob to C3, I have a feeling that will probably change also.

    I've gotten as far as opening the game in r401.

    Thanks.

  • I tried the r401, it was fine on pc, but lags out completely on mobile. Both in remote preview and when exported to google play.

Post reply
Return to board index
Jump to:
Order by:
Duplicate Topics
Posts
Views
Last Post
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)