Appodeal Error code 256

Hi

MacOS 11.3.1 and 3656 Solar2D trying to build for android.

When I build using beta appodeal everything is fine.
When I build using the stable version I get error message.

Last week the same app, with same setup and stable appodeal version was fine.

The error message:

BUILD SUCCESSFUL
Total time: 2 seconds
Sep 24 18:19:47.435 FAILURE: Build failed with an exception.

                * What went wrong:
                Execution failed for task ':App:checkReleaseDuplicateClasses'.
                > A failure occurred while executing com.android.build.gradle.internal.tasks.CheckDuplicatesRunnable
                   > Duplicate class com.google.common.util.concurrent.ListenableFuture found in modules jetified-guava-20.0 (com.google.guava:guava:20.0) and jetified-listenablefuture-1.0 (com.google.guava:listenablefuture:1.0)
                     
                     Go to the documentation to learn how to <a href="d.android.com/r/tools/classpath-sync-errors">Fix dependency resolution errors</a>.
                
                * 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 25s

Sep 24 18:19:47.863 Android build failed (256) after 31 seconds
Sep 24 18:19:48.294 ERROR: Build Failed: Error code: 256

That is the guava mess. What other plugins do you have in your build settings? Try adding the GPGSv2 even if you are not using it. That plugin has the hack from Google.

Hi agramonte

I already use gpgsv2.

Plugins list in build settings:

  • appodeal
  • pollfish
  • gpgsv2
  • utf8

Can you try building without gpgsv2?

Hi agramonte

I removed gpgsv2 and the build was successful.
The apk was created without any errors.

But I really need gpgsv2 in my game for saving / loading player’s progress :slight_smile:

Today I can build without problems.
It was solar2d server side problem.

Can anyone explain why this things happen?
Is there a way to understand if it’s programmer’s issue or it’s solar2d side?

Looks like Scott made the change 12 hours ago to make it work:

1 Like