Learn what Felgo offers to help your business succeed. Start your free evaluation today! Felgo for Your Business


OverviewFelgo 3 Support (Qt 5) › Can't deploy Android app to device after 2.13.2

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #17319


    Hi Felgo,
    So had issues desribed here https://felgo.com/developers/forums/t/error-compiling-after-new-update-2-13-2.
    Total re-install of Felgo helped with Android and Desktop.
    App runs on desktop but unfortunately can’t deploy it to Android device.
    So following https://felgo.com/doc/vplay-updates/#android I did all the changes.
    Unfortunately during deployment to Android device getting:

    Total time: 6.37 secs
    * Where:
    Build file '{hidden}/{hidden}_v7a_GCC_4_9_Qt_5_9_2_for_Android_armv7-Debug/android-build/build.gradle' line: 19
    * What went wrong:
    A problem occurred evaluating root project 'android-build'.
    > Failed to apply plugin [id 'com.android.application']
       > Minimum supported Gradle version is 3.3. Current version is 2.14.1. If using the gradle wrapper, 
    try editing the distributionUrl in
     {hidden}/{hidden}-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_2_for_Android_armv7-Debug/android-build/gradle/wrapper/gradle-wrapper.properties to gradle-3.3-all.zip


    So I change the gradle properties file to gradle-3.3-all.zip as it said in the docs and the error suggests.
    This was a common issue so it’s nothing new to me.
    But guess what happens next after the upgrade?
    The next time I try to deploy the app … the value is becoming reverted back to old version!
    It doesn’t matter that I change it since it is reverted all the time and I get the same error all the time.




    Some clarification, I am on 64 bit Linux and the device I am trying to deploy is Samsung S3 Anrdoid 4.3.
    Didn’t test iOS deployment yet after the upgrade but will try to do it soon.


    Felgo Team

    Hi Marcin,

    sorry for your troubles after the new update!

    Re-installing is a good solution when it comes to issues after updates with bigger Kit Changes. Unfortunately the Qt MaintenanceTool has troubles to resolve dependencies correctly sometimes, which is why the installation can get messed up (with e.g. the missing/wrong modules).

    About the gradle-wrapper problem:
    We updated some Felgo Plugin versions, which also affects the required gradle version. If the fixed gradle-wrapper.properties file gets reverted when you are trying to build, you probably fixed it at the wrong location. The build folder is recreated when building, so the changed gradle-wrapper gets overwritten. Your project maybe already has a custom android/gradle/wrapper/gradle-wrapper.properties file, or you can create one there.

    This file will be used when building the project then.

    Does this solve your issue?



    Hi Günther,
    Yes, you are right.
    Wasn’t aware of this version of gradle config.
    This fixes the issue.

    In the end it is welcome change because I don’t need to change it every time I clean build directory and it stays in repository.

Viewing 4 posts - 1 through 4 (of 4 total)

RSS feed for this thread

You must be logged in to reply to this topic.

Qt_Technology_Partner_RGB_475 Qt_Service_Partner_RGB_475_padded