Skip to main content

Android Integration FAQs

Here are some of the frequently asked questions while integrating the Yodo1 MAS SDK on Android.

Resolution Issues​

What if the resolution fails while the resolver downloads the dependencies?​

If the resolution fails while the resolver downloads the dependencies, try using a VPN.

Ad Loading Issues​

What are the common issues with ad loading for live apps?​

  • For live apps, ensure that the app-ads.txt file is updated. Please see more details here: app-ads.txt.
  • Verify that the integration is proper. Please refer to this document: Getting Started.
  • Make sure that the minify settings are disabled under player settings.
tip

Note: We don't support cash making applications or real money applications. If your application falls into this category, ads will not be shown. Please check out our privacy policy for more details.

What about ad loading issues for apps that are not live yet?​

  • For apps that are not live yet, ensure you are testing the integration using test ads. Please see more details here: Testing Ads.
  • Verify that the test device is added in the MAS dashboard.
  • Ensure that test mode is enabled for the game in MAS dashboard.
  • Verify that privacy policy settings are enabled. Please see more details here: Legal.
  • Make sure that the minify settings are disabled under player settings.

Build Issues​

What steps should I take if I encounter an error during the build process?​

If you encounter an error during the build process, follow these steps:

  • Remove all the existing ad networks.

  • If you were previously using AdMob. Verify that AdMob is also removed in Package Manager.

  • Compare your Android resolver settings with the following.

    Click to enlarge image

  • Confirm your Player settings. Please note that you can target API level 31/32 to be compatible with Android 12 devices.

  • For "Duplicate Class" errors, use these custom build settings.

    Click to enlarge image

  • Remove all jar/aar files under Plugins/Android. Then force resolve.

  • If you get a FileNotFoundException error while compiling the aab file, like below:

    Error information: FileNotFoundException: Temp/gradleOut/launcher/build/outputs/bundle/release/launcher.aab does not exist

    You must check "Custom Launcher Gradle Template" in the Players settings. Then open launcherTemplate.gradle file and in defaultConfig, add the following code:

    Click to enlarge image
    tasks.whenTaskAdded { task ->
        if (task.name.startsWith("bundle")) {
            def renameTaskName = "rename${task.name.capitalize()}Aab"
            def flavor = task.name.substring("bundle".length()).uncapitalize()
            tasks.create(renameTaskName, Copy) {
                def path = "${buildDir}/outputs/bundle/${flavor}/"
                from(path)
                include "launcher-release.aab"
                destinationDir file("${buildDir}/outputs/bundle/${flavor}/")
                rename "launcher-release.aab", "launcher.aab"
            }
            task.finalizedBy(renameTaskName)
        }
    }
    Click to enlarge image

Testing Issues (Ads, and Crashes)​

What should I do if I don't see ads while testing or if my app is crashing?​

If you don't see ads while testing or if your app is crashing, verify all the items in this checklist:

  1. The adaptive banners are not enabled by default. Please get in touch with support through the dashboard if you wish to use them.
  2. Ensure your device ID is added to the MAS dashboard under "Management > Testing".
  3. Confirm that the ad formats are enabled for your game or app.
  4. Ensure you are using the right App Key, AdMob ID, and Bundle ID from MAS Dashboard.
  5. Make sure that the minify settings are disabled under player settings.
  6. If minify settings must be enabled, please check the ProGuard guide.
  7. Ensure your app-ads.txt file is updated and hosted on your store listing's primary domain.