Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

extra debug folder confuses deploy step (android)



  • Hello,

    I have a problem with my app that is suddenly not building anymore. It must a change introduced by me or a program, but I don't know which (and git diff is not helpful either).

    That's what I did:

    I started with an empty Qt Quick application. I added the sample Java Activity from Android Studio to the Qt project. In order to add some needed dependencies for the Java Activity, I generated the "Android files" from QtCreator, giving me some Gradle files and an AndroidManifest. I changed the AndroidManifest to comply with the new classes and added some dependencies in the Gradle files. I had to add the Google repository, so I also specified a higher version for Gradle (4.4) in gradle-wrapper.properties.

    All of a sudden however, the project is not building anymore. I get the following error:

    ...build-*_qt-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_0_for_Android_armv7-Debug/android-build//build/outputs/apk/android-build-debug.apk : No such file or directory
    

    Qt Creator is right. In the folder, there is an extra debug folder in which the apk resides. Actually, Qt Creator should be looking for...

    ...build-*_qt-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_0_for_Android_armv7-Debug/android-build//build/outputs/apk/debug/android-build-debug.apk
    

    ... but it doesn't.

    I tried after removing all build folders and the .pro.user file. Still, the error remains. Has anyone seen such an error before? Where are those paths set?



  • Ok, I have to add that it does not work with a new blank Qt project without any changes. If I try to deploy to Android, I get the same error. I can successfully deploy the Android samples, though. They are located in a path without the extra debug folder. So is there anything different between the simple Qt Quick projects and the Qt Android examples?



  • I reinstalled Qt and now it works .. sigh


Log in to reply