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. errors when attempting to debug an iOS app
QtWS25 Last Chance

errors when attempting to debug an iOS app

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
1 Posts 1 Posters 233 Views
  • 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.
  • V Offline
    V Offline
    Vega4
    wrote on 15 May 2021, 22:28 last edited by Vega4
    #1

    The app gets deployed by Qt Creator. It runs without debugger just fine. When debugging is attempted it goes on and on like follows:

    created qml server
    00:12:58: Debugging /Users/anonymous/Documents/MyApp/build-MyApp-Qt_5_15_2_for_iOS-Debug/Debug-iphoneos/MyApp.app/MyApp -qmljsdebugger=port:59210,block,services:DebugMessages,QmlDebugger,V8Debugger,QmlInspector,DebugTranslation ...
    handleNewRelayConnection
    setting up relayer for new connection
    tryRemoteConnect
    TransferAppSession(34534534fdgdfg565456456dfgdfgdfg, /Users/anonymous/Documents/MyApp/build-MyApp-Qt_5_15_2_for_iOS-Debug/Debug-iphoneos/MyApp.app)connectByPort on device 34534534fdgdfg565456456dfgdfgdfg port 30002 failed, AMDeviceStartService returned 61
    tryRemoteConnect *failed* on remote port 30002
    handleNewRelayConnection
    setting up relayer for new connection
    tryRemoteConnect
    TransferAppSession(34534534fdgdfg565456456dfgdfgdfg, /Users/anonymous/Documents/MyApp/build-MyApp-Qt_5_15_2_for_iOS-Debug/Debug-iphoneos/MyApp.app)connectByPort on device 34534534fdgdfg565456456dfgdfgdfg port 30002 failed, AMDeviceStartService returned 61
    tryRemoteConnect *failed* on remote port 30002
    handleNewRelayConnection
    setting up relayer for new connection
    tryRemoteConnect
    

    Ideas?

    latest iOS, Mac is running latest BigSur

    Update: This seems to happen only when QML debugging is enabled. Without QML debugging everything works just fine.

    1 Reply Last reply
    0

    1/1

    15 May 2021, 22:28

    • Login

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