Info

  • Official Official addon
  • Built in Built-in addon
  • Allows monetisation of your creations

Owners

Ashley's avatar
Ashley Construct Team Founder

Description

Handle AdMob adverts for Cordova on iOS and Android.

Discussion

  • 39 Comments

  • Order by
Want to leave a comment? Login or Register an account!

  • when i export from construct 3 to cordova, i can't build APK using cordovaCLI, but when i remove "construct-mobile-advert" it builds normally.

    It had never happened to me before, it just happened this week.

    • After several attempts and a pain in the head, I found where the problem was.

      After exporting the game from Construct 3 and opening the "config.xml" file, I found that the "construct-mobile-advert" version was 1.7.2, and on npmjs.com the latest version is 1.7.3. So I changed it to "construct-mobile-advert" spec = "1.7.3" and everything worked fine.

  • Only test ads are showing but no ads show when test mode is off. Please share a tutorial or "how to" guide.

  • not work with runtime c3

  • Not sure about everybody else but make sure your app ID,android,ios,..etc is correct for the ad mob plugin that what solved my problem.

  • not working

  • Hello, when i use this plugin to display ads on my game, the game crash when i launch it..

    But when i remove the plugin the game work perfectly..

    Any fix ?

  • Not work in c3, please how we can fix this problem??

  • Are we going to update the addon to its newest version?

    "com.google.android.gms:play-services-ads-lite:20.6.0

    Google Mobile Ads (GMA) SDK (com.google.android.gms:play-services-ads-lite) has added this note for SDK version 20.6.0:

    As of June 30th 2024, this version is sunset. For more information, please visit developers.google.com/admob/android/deprecation.

    From October 29, 2024 00:00 (UTC) you won't be able to release new versions of your app containing this SDK version to production or open testing"

    Thanks

  • The is the fix sent to me from Google (Part 2 of 2)

    5. Under the new release page, you can:

      • Upload a new, compliant version code and roll out a new release to 100% to completely deactivate the non-compliant version.
      • Roll out a blank release (i.e., a release with all version codes under the Deactivated app bundles section and no version codes under the New app bundles or Retained app bundles sections) and roll it out to 100%.

    6. Select Save.

    7. When you've finished preparing your release, select Review release.

    If the non-compliant version code is released to multiple tracks, repeat steps 3-7 in each track.

  • The is the fix sent to me from Google (Part 1 of 2)

    In addition, if you want to deactivate a non-compliant version code. Please follow the below steps:

    1. Go to your Play Console.
    2. Select the app.
    3. Go to the track where the non-compliant version code is active.
      • You can confirm where the non-compliant version code is active by going to:
        1. Release > Releases overview > Add filter > Version code > Search > Apply
        2. Release > App bundle explorer > Search by version code or name > View app version (right arrow symbol)
    4. Near the top right of the page, click Create new release (you may need to click Manage track first).
      • If the release with the violating version code is in a draft state, discard the release.

    (Part 2 of 2) here v

    construct.net/en/comments/68513

  • Load more comments (23 replies)