Build failed exporting to Android

0 favourites
  • 4 posts
From the Asset Store
Isometric Stategy Roleplay Game Building and Streets Pack.
  • I have a project developed with and old R356 C3 version that has been exported to android in the past.

    Today I've opened it again with the version R408 and tried to export it to Android again and I received the error I'm reporting here below.

    The Minify mode is set to "none" and I try to export both a Debug APK or the AAP

    The application works correctly on my PC but export gives me the error.

    Any idea on what could be the origin of the cause?

    UPDATE:

    - I'm able to export the R356 project with the R388-2 Stable release

    - I'm not able to export the R356 project with the R397-2 Stable release

    UPDATE2:

    - Last version able to export the APK was R396. Starting from the R397-2 I get the error below.

    "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 729ms

    1 actionable task: 1 executed

    Subproject Path: CordovaLib

    Subproject Path: app

    Task :app:preBuild UP-TO-DATE

    Task :app:preReleaseBuild UP-TO-DATE

    Task :app:generateReleaseResValues

    Task :CordovaLib:preBuild UP-TO-DATE

    Task :CordovaLib:preReleaseBuild UP-TO-DATE

    Task :CordovaLib:generateReleaseResValues

    Task :CordovaLib:generateReleaseResources

    Task :CordovaLib:packageReleaseResources

    Task :app:mapReleaseSourceSetPaths

    Task :app:generateReleaseResources

    Task :app:createReleaseCompatibleScreenManifests

    Task :app:extractDeepLinksRelease

    Task :CordovaLib:extractDeepLinksRelease

    Task :CordovaLib:writeReleaseAarMetadata

    Task :CordovaLib:processReleaseManifest

    Task :app:checkReleaseAarMetadata

    Task :app:mergeReleaseResources

    Task :app:processReleaseMainManifest

    Task :app:processReleaseManifest

    Task :app:processApplicationManifestReleaseForBundle

    Task :app:packageReleaseResources

    Task :app:parseReleaseLocalResources

    Task :app:processReleaseManifestForPackage

    Task :CordovaLib:compileReleaseLibraryResources

    Task :app:extractReleaseVersionControlInfo

    Task :CordovaLib:parseReleaseLocalResources

    Task :CordovaLib:generateReleaseRFile

    Task :CordovaLib:javaPreCompileRelease

    Task :app:processReleaseResources FAILED

    25 actionable tasks: 25 executed

    FAILURE: Build failed with an exception.

    * What went wrong:

    Execution failed for task ':app:processReleaseResources'.

    Could not resolve all files for configuration ':app:releaseCompileClasspath'.

    Could not resolve com.google.android.ump:user-messaging-platform:1.0.0+.

    Required by:

    project :app

    Failed to list versions for com.google.android.ump:user-messaging-platform.

    Unable to load Maven meta-data from https:/~~/maven-metadata.xml.

    Could not GET 'https:/~~/maven-metadata.xml'. Received status code 403 from server: Forbidden

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

    Command failed with exit code 1: ~~/gradlew :app:bundleRelease"

    Tagged:

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • AshleyCould you please have a quick look at the log above and give me a suggestion to on what might be the problem?

  • Could not resolve com.google.android.ump:user-messaging-platform:1.0.0+. Required by: project :app Failed to list versions for com.google.android.ump:user-messaging-platform.

    Fix build cordova cli

    cordova plugin add cordova-plugin-consent --save --variable UMP_VERSION=2.2.0

    Fix with addon sdk

  • I'm afraid as in this case it's often not possible to tell what went wrong from only a log. It could be a problem caused by a third-party addon your project uses, in which case you'd need to contact the addon developer for support. Otherwise if it's only using Construct official features, we'd need a full bug report to investigate (including e.g. a sample project).

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)