Appodeal SDK 3.4.2released cause android build failed

vincenthawk · February 25, 2025, 5:03am

Hi there,
I build android apk sucessfully yesterday.
But failed today with no changes of codes.

Execution failed for task ':App:checkReleaseAarMetadata'.
> Could not resolve all files for configuration ':App:releaseRuntimeClasspath'.
   > Could not find com.appodeal.ads:sdk:3.4.2s.0.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/com/appodeal/ads/sdk/3.4.2s.0/sdk-3.4.2s.0.pom
       - https://jcenter.bintray.com/com/appodeal/ads/sdk/3.4.2s.0/sdk-3.4.2s.0.pom
       - https://repo.maven.apache.org/maven2/com/appodeal/ads/sdk/3.4.2s.0/sdk-3.4.2s.0.pom
       - file:/Users/vincentchen/Library/Application%20Support/Corona/Native/Corona/android/lib/gradle/sdk-3.4.2s.0.jar
       - file:/Users/vincentchen/Library/Application%20Support/Corona/Native/Corona/android/lib/gradle/sdk.jar
       - file:/Users/vincentchen/Library/Application%20Support/Corona/Native/Corona/android/lib/Corona/libs/sdk-3.4.2s.0.jar
       - file:/Users/vincentchen/Library/Application%20Support/Corona/Native/Corona/android/lib/Corona/libs/sdk.jar
       - https://artifactory.appodeal.com/appodeal/com/appodeal/ads/sdk/3.4.2s.0/sdk-3.4.2s.0.pom
     Required by:
         project :App

* 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.

Is it something wrong with the appodeal plugin or else?
Please help me with this issue
Thanks!

Vincent

colinmorgan · February 25, 2025, 8:06am

Have you checked your plugin folder to make sure it downloaded successfully?

vincenthawk · February 25, 2025, 8:10am

Yes.

colinmorgan · February 25, 2025, 10:51am

My Appodeal folder looks like this:

Maybe try throwing that .tgz file away, restart your computer and then try a build. That should force the plugin to re-download.

vincenthawk · February 25, 2025, 11:19am

Hi , thanks for your quick reply.
I’ve delete all the files in ‘/Library/Application Support/Corona/Simulator/Plugins/’
The build still failed, and same error message.

Can you build the android version with appodeal sucessfully?
May I see the build.settings related the appodeal?

Also there is difference of the Appodeal folder between yours and mine, there is no info.txt of mine.

I am using the MBP M1, 2020.
Corona simulator Version 2025.3717

vincenthawk · February 25, 2025, 2:26pm

I try to build the sample project GitHub - coronalabs/plugins-sample-appodeal , the ios version was built sucessfully, but the android version got the same error.

* What went wrong:
Execution failed for task ':App:checkReleaseAarMetadata'.
> Could not resolve all files for configuration ':App:releaseRuntimeClasspath'.
   > Could not find com.appodeal.ads:sdk:3.4.2s.0.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/com/appodeal/ads/sdk/3.4.2s.0/sdk-3.4.2s.0.pom
       - https://jcenter.bintray.com/com/appodeal/ads/sdk/3.4.2s.0/sdk-3.4.2s.0.pom
       - https://repo.maven.apache.org/maven2/com/appodeal/ads/sdk/3.4.2s.0/sdk-3.4.2s.0.pom
       - file:/Users/vincentchen/Library/Application%20Support/Corona/Native/Corona/android/lib/gradle/sdk-3.4.2s.0.jar
       - file:/Users/vincentchen/Library/Application%20Support/Corona/Native/Corona/android/lib/gradle/sdk.jar
       - file:/Users/vincentchen/Library/Application%20Support/Corona/Native/Corona/android/lib/Corona/libs/sdk-3.4.2s.0.jar
       - file:/Users/vincentchen/Library/Application%20Support/Corona/Native/Corona/android/lib/Corona/libs/sdk.jar
       - https://artifactory.appodeal.com/appodeal/com/appodeal/ads/sdk/3.4.2s.0/sdk-3.4.2s.0.pom
     Required by:
         project :App

* 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 31s

Feb 25 22:24:33.534: Android build failed (256) after 36 seconds
Feb 25 22:24:33.928: ERROR: Build Failed: Error code: 256

Please help me with this issue. Thanks!

Vincent
@Scott_Harrison

colinmorgan · February 25, 2025, 4:25pm

My settings are of no help to practically anybody. I version lock all my plugins and only update Solar2D versions when I absolutely have to. I’m typically six months to a year behind anything that’s being actively worked on.

vincenthawk · February 25, 2025, 4:45pm

Thanks , anyway.
Would you show me how to do the “version lock”?
It sounds very useful.

Scott_Harrison · February 25, 2025, 6:51pm

We’ll take a look at this when I get a chance

colinmorgan · February 25, 2025, 9:14pm

It’s super easy. For example:

["plugin.admob"] = { publisherId = "com.coronalabs", version = "v38", },

To find the plugin version, go here:

Find your plugin, click on it, and then click on Updated: some date.

That will take you to the GitHub repository for that plugin. From there, click on the word “Releases” in the right rail. (Not “Release vXX”- click the word “Releases” directly above it.) Clicking there will take you to the release list with the version number, what was updated and the date. You can pick your release version and set that version in build.settings.

Version locking means you’re not obligated to use the latest-and-greatest. When you find a version that works, you can stick with it until you decide to move forward. We put out content updates for multiple apps every month, and this way I don’t have to worry that right before I have a scheduled update, some plugin update will have introduce a breaking issue with my build.

Scott_Harrison · February 25, 2025, 9:45pm

I just pushed a new release with fixes, I apologize for the issue, there was a typo in gradle

vincenthawk · February 26, 2025, 6:33am

Hi Scott

Thank you for fixing the problem quickly

Vincent

vincenthawk · February 26, 2025, 6:37am

Hi Colin,

Thank you for your patient explanation and sharing, which taught me a good version management method.

Vincent