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

aidle.exe crash when running on real Android device



  • Hello,
    I have problems when I try to run an application on a real Android device on Qt Creator (Samsung Galaxy Grand Prime, Android Version 5.1.1).
    Everything is fine with Android Studio (I can run on an emulator and on my Android device), and I can run on an emulator on Qt Creator.

    When I try to run on my Android device on Qt Creator, I get this error (sorry it is in french) :

    0_1554800549545_0a7c20e0-928f-4bac-9fa2-9cfd94267d4f-image.png

    0_1554806198229_68afc470-c93f-489b-a185-574522893ccf-image.png

    Versions:
    Qt - 4.8.1
    Qt Creator - 5.12.1
    Jdk 1.8.0_202
    SDK - 26.1.1
    NDK - 19.2.5345600

    If someone can help me, I didn't fidn anything on internet for this specific error
    Thanks


  • Moderators

    Try different SDK version, you are not using a stable SDK build tools.



  • I have deleted SDK build tools version 29.0.0 rc2, and changed buildToolsVersion in build.gradle file, but when I compile my application, it installs SDK build tools 29.0.0 rc2. Any idea why?

    0_1554883350405_36815e2a-e6c4-4042-94c5-6cdf7833eb86-image.png

    Here are my build.gradle and .properties files :

    0_1554883769093_28c5b03a-9a7a-4442-96c3-e12d49bafc18-image.png

    0_1554883744401_a685a557-ad99-4869-8b4b-f2bc4c5ac82f-image.png


  • Moderators

    Huh, weird. I have no idea why it happens sorry.



  • I found a way to avoid the "aidle .exe crash ..." error. It is definitely caused by the SDK Build Tools version 29.0.0 rc2. When I uninstalled the version 29.0.0 rc2 of the SDK Build Tools, I still had the error for my current project.

    But when I uninstalled the SDK Build Tools version 29.0.0 rc2, and then created a new Android project on Qt Creator, it worked. (To be sure that the error was caused by this version of SDK Build Tools, I have installed it again, created a new Android project on Qt Creator, and I had the error again)

    Thanks a lot @sierdzio for your help


Log in to reply