Android Build fails can't ger support-v4/maven-metadata.xml

Vega4

Hello everyone!

We've booted up a VM with QT frozen state, with project, which has not been used for months after recent upload to Google Play.

With high hopes that everything would thus go fine.. it did not.

the gist:

:-1: error: 
            > Could not get resource 'https://jcenter.bintray.com/com/android/support/support-v4/maven-metadata.xml'.

More Logs:

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':mergeDebugResources'.
> Could not resolve all files for configuration ':debugRuntimeClasspath'.
   > Could not resolve com.android.support:support-v4:24.+.
     Required by:
         project :
      > Failed to list versions for com.android.support:support-v4.
         > Unable to load Maven meta-data from https://jcenter.bintray.com/com/android/support/support-v4/maven-metadata.xml.
            > Could not get resource 'https://jcenter.bintray.com/com/android/support/support-v4/maven-metadata.xml'.
               > Could not GET 'https://jcenter.bintray.com/com/android/support/support-v4/maven-metadata.xml'.
                  > Read timed out

The URL https://jcenter.bintray.com/com/android/support/support-v4/maven-metadata.xml is also not available to a web-browser which returns 403 Forbidden.

We've upgraded QT to Qt Creator 6.0.1 in hopes this would solve the issue it did not.

Ideas how to approach this?

Kindly thank you for reading this.

Vega4

Here's build.gradle:

buildscript {
    repositories {
        google()
        jcenter()
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:3.5.0'
    }
}

allprojects {
    repositories {
        google()
        jcenter()
		maven {
            url 'https://maven.google.com'
        }
    }
}

apply plugin: 'com.android.application'

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    compile 'com.android.support:appcompat-v7:28.0.0'
    compile 'com.android.support:design:28.0.0'
    compile 'com.android.support:support-v4:24.+' 
}

android {
    /*******************************************************
     * The following variables:
     * - androidBuildToolsVersion,
     * - androidCompileSdkVersion
     * - qt5AndroidDir - holds the path to qt android files
     *                   needed to build any Qt application
     *                   on Android.
     *
     * are defined in gradle.properties file. This file is
     * updated by QtCreator and androiddeployqt tools.
     * Changing them manually might break the compilation!
     *******************************************************/

    compileSdkVersion androidCompileSdkVersion.toInteger()

    buildToolsVersion androidBuildToolsVersion

    sourceSets {
        main {
            manifest.srcFile 'AndroidManifest.xml'
            java.srcDirs = [qt5AndroidDir + '/src', 'src', 'java']
            aidl.srcDirs = [qt5AndroidDir + '/src', 'src', 'aidl']
            res.srcDirs = [qt5AndroidDir + '/res', 'res']
            resources.srcDirs = ['src']
            renderscript.srcDirs = ['src']
            assets.srcDirs = ['assets']
            jniLibs.srcDirs = ['libs']
       }
    }

    lintOptions {
        abortOnError false
    }
}

Vega4

First of all I believe QT is GREAT.

It allows one to accomplish GREAT work, even though we used to have bumpy rides with it over the years (bugs in framework, Creator hitting the fan).

One thing is for sure though. Which made us loose lots of time. - the need for additional gluing between elements always used to be very imminent. I know it can now autonomously download Android SDK and stuff but still we don't even EXPECT that...it never was like ..one common language, with QML portable among many platforms, without the need to be using additional native Mac OS X deployment tools and stuff. Was it? But you can't really attach to a running process on Android and stuff... half of UI options around these lines do no really work...it even says 'non implemented' once you click on it, in log files.

Once you get everything setup and running for the project. It's fine.

Until sh** happens, and it WILL, with some of the internal files and you have no idea how to approach it.

Suddenly it turns out some files can't be opened.. and suddenly you need to be well familiar with native Android, Gradle, Maven, everything.

Long ago we began to employ virtualization to offset for that. Turned out to be the best choice.

Anyhow, not to cry a river:
in file gradle-wrapper.properties changed version to:
https://services.gradle.org/distributions/gradle-6.7-bin.zip

no idea if that's the right one. It works. Good luck to everyone.