[Solved] QtCreator deployment for Android fails with timeout



  • Hi everybody!

    Until today I was able to find an answer to all of my questions here in this great forum, but now I got a problem that appeared very recently and no one else seems to be running in it, yet.

    I have set up Qt 5.3 on Windows 7/64bit with all latest updates and do some development for an Android target. Until yesterday everything went fine. Compiling, deployment and debugging was possible on the emulator as well as on a real android device.

    But since I did some Windows-Updates yesterday the deployment process is not working any more! I am not sure if these updates are the reason, but I do not remember to make any other changes to my build environment.

    To reproduce the issue I do the following:

    Start the deployment process by clicking "Deploy All"
    Then select the desired target device as usual.
    Then this message appears in the "Compile Output" panel:

    @13:40:11: Running steps for project velodashC...
    13:40:11: Configuration unchanged, skipping qmake step.
    13:40:11: Starting: "G:\Qt_online\Tools\mingw482_32\bin\mingw32-make.exe" -j 8
    mingw32-make: Nothing to be done for 'first'.
    13:40:12: The process "G:\Qt_online\Tools\mingw482_32\bin\mingw32-make.exe" exited normally.
    13:40:12: Starting: "G:\Qt_online\Tools\mingw482_32\bin\mingw32-make.exe" INSTALL_ROOT="F:\\\\T2FT\\\\build\\\\velodashC\\\\Q53Aa7\\\\debug\\\\android-build" install
    copy /y "libvelodashC.so" "F:\T2FT\build\velodashC\Q53Aa7\debug\android-build\libs\armeabi-v7a\libvelodashC.so"
    1 Datei(en) kopiert.@

    And after a timeout of about 1 minute, during which QtCreator is not reacting to any user input, the "Compile Output" panel shows the following:

    @13:40:11: Running steps for project velodashC...
    13:40:11: Configuration unchanged, skipping qmake step.
    13:40:11: Starting: "G:\Qt_online\Tools\mingw482_32\bin\mingw32-make.exe" -j 8
    mingw32-make: Nothing to be done for 'first'.
    13:40:12: The process "G:\Qt_online\Tools\mingw482_32\bin\mingw32-make.exe" exited normally.
    13:40:12: Starting: "G:\Qt_online\Tools\mingw482_32\bin\mingw32-make.exe" INSTALL_ROOT="F:\\\\T2FT\\\\build\\\\velodashC\\\\Q53Aa7\\\\debug\\\\android-build" install
    copy /y "libvelodashC.so" "F:\T2FT\build\velodashC\Q53Aa7\debug\android-build\libs\armeabi-v7a\libvelodashC.so"
    1 Datei(en) kopiert.
    13:40:13: The process "G:\Qt_online\Tools\mingw482_32\bin\mingw32-make.exe" exited normally.
    Error while building/deploying project velodashC (kit: Android für armeabi-v7a (GCC 4.8, Qt 5.3.0))
    When executing step 'Deployment auf Android-Gerät'
    13:42:14: Elapsed time: 02:03.@

    So it looks like "make install" runs fine (although the success message come after the timeout), but androiddeployqt gets never called, this is very strange...

    As said already, everything was fine yesterday, and the only changes I made (at least what I can remember) are the windows updates.

    Rebboting the PC, deleting and recreating all build directories and the AndroidManifest.xml did not help so far.

    So far I can create a usable APK by running "androiddeployqt" tool manually. But to make this work I have to use a slightly different "INSTALL_ROOT" environment variable than QtCreator uses. I have to omit the "android-build" part of the path to make androiddeployqt find the libvelodashC.so target application.

    Has anyone else made this experience, or even a solution? Thank you very much for your support!

    [Edit]
    Deployment to actual android device is still working well. So there seems to be a problem with AVD.
    [/Edit]

    Thomas



  • Looks like I hoaxed myself. Problem was not the Windows Updates, but a slightly different set-up in comparison to my first runs.

    When it worked, I had the AVD opened and a real device attached. So both the emulation and the deployment to a real device worked.

    When it failed, I had no real device attached and relied on the AVD to be started automatically by QtCreator - but that is definitely not the case for the newest Android SDK/NDK, which is what I am using.

    On my other development machine I run arch linux and there everything works like a charm. So I got a little confused about automatic AVD start by QtCreator (working on Linux, not working on Windows).

    As a net result: When I start the AVD manually everything is fine.


  • Moderators

    Nice investigation, thanks for sharing.


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.