Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Debugging for android/iOS mode is always fail in my Qt's Enterprise Version!
Forum Updated to NodeBB v4.3 + New Features

Debugging for android/iOS mode is always fail in my Qt's Enterprise Version!

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
7 Posts 3 Posters 1.9k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • zenghsingZ Offline
    zenghsingZ Offline
    zenghsing
    wrote on last edited by zenghsing
    #1

    I use Qt Creator.

    I deploy my code to my android phone and using debgging mode.

    But the bugging for android mode is always fail in my Qt's Enterprise Version!

    It shows:

    Connecting to remote server failed: Remote connection closed

    1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #2

      Hi,

      Since you have an enterprise license, you should contact the Qt Company support people.

      In any case, are you sure your application starts ?

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      1 Reply Last reply
      0
      • zenghsingZ Offline
        zenghsingZ Offline
        zenghsing
        wrote on last edited by
        #3

        @SGaist said:

        enterprise license

        All function they support for enterprise license is the same with the Free - Qt license.

        I had contact the Qt Company support people many times before.

        And the support center for enterprise license is only the place for reporting Qt's Bug. They won't answer your problem.

        They told me I should post my problem here...

        Hence, I give up to use the support center.

        But it shows "Connecting to remote server failed: Remote connection closed" when I deploy my code to my android in Debugger mode.

        And then, my application stares in my android.

        I found it seem a old problem.

        https://forum.qt.io/topic/47624/debugging-android-setup/3

        1 Reply Last reply
        0
        • SGaistS Offline
          SGaistS Offline
          SGaist
          Lifetime Qt Champion
          wrote on last edited by
          #4

          Which version of the SDK/NDK are you using ?

          Also, what do you get on the application output window when you start your application ?

          Interested in AI ? www.idiap.ch
          Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

          zenghsingZ 1 Reply Last reply
          0
          • SGaistS SGaist

            Which version of the SDK/NDK are you using ?

            Also, what do you get on the application output window when you start your application ?

            zenghsingZ Offline
            zenghsingZ Offline
            zenghsing
            wrote on last edited by
            #5

            @SGaist said:

            Which version of the SDK/NDK are you using ?

            Also, what do you get on the application output window when you start your application ?

            Hi, SGaist:

            I am not sure how to check the version of the SDK and NDK.
            But I try to check the Android properity in Preferences in QCreator.
            SDK location: ....../android-sdk-macosx
            NDK location:..../android-ndk-r10d

            I did not find the version for SDK in readme.text when I go to the folder "....../android-sdk-macosx".

            I want to get multi-touch event on the screen.(android /iOS )
            But the event in mac and android is pretty different.
            One is QNativeGesture and the other is QTouchBegin/...

            https://www.newmobilelife.com/wp-content/uploads/2015/03/2015-13-in-macbook-pro-teardown_01.jpg

            1 Reply Last reply
            0
            • M Offline
              M Offline
              mvuori
              wrote on last edited by
              #6

              More relevant than the platform SDK version is the Qt SDK version, which is the same as the Qt version. If I remember right, some recent beta versions of the community version of Qt had this problem and the only fix was to wait for the next version (or revert to the previous one). (Qt seems to have a habit of breaking debugging every once in a while...)

              But first I'd check that you have the latest version installed. Your NDK could probably be updated too.

              Of course, something may have gotten corrupted and a reinstall is a fast and safe fix for that. There could also be something wrong in you general computing environment and you could, for comparison, install the community version and see how that behaves.

              1 Reply Last reply
              0
              • SGaistS Offline
                SGaistS Offline
                SGaist
                Lifetime Qt Champion
                wrote on last edited by
                #7

                @mvuori It's not so much that debugging breaks but that the debugger used change from one version of the provided SDK to the other.

                Additionally to the Qt version, what version of Android does your device run ?

                Interested in AI ? www.idiap.ch
                Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                1 Reply Last reply
                0

                • Login

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Users
                • Groups
                • Search
                • Get Qt Extensions
                • Unsolved