ERROR: Could not connect to lockdownd, error code -3

Solar2D iOS
#1

Hi there,

I’m trying to update some older apps that I created 4 years ago to run on iOS11.

I have the latest xCode 9.x beta installed (14/9/17), and latest Corona dev build but I’m unable to get the app to copy to my iPhone 6s which is running iOS11 (Gold Master).

I’ve been getting:

ERROR: Could not connect to lockdownd, error code -3

ERROR: Could not connect to lockdownd, error code -3

ERROR: no USB connected devices detected (if one is attached, try reconnecting it)

 

I’m able to build directly and copy to the phone directly from xCode, but not Corona.

 

Any help will be very welcome…

 

Cheers - Dom

#2

The command line installer we use to install from Corona to Device is broken in iOS 11. Our engineers are looking into solutions. For now you would just either chose “Show in Finder” or “Do Nothing” and use Xcode’s Device’s window to install the app.

Rob

#3

Rob - Thanks for the prompt reply - I’ll try that out…Cheers - Dom

#4

i have the same trouble… hope it will quickly be fixed :frowning:

#5

Same issue here - any eta on a fix?

#6

Unfortunately we don’t have an ETA for this.  

#7

Same problem! I have subscribed to this topic for hopefully positive updates. 

#8

According to the release notes, we solved this in the latest daily build 3157.  Give that a try!

Rob

#9

Hurrah… back in business.  3157 works fine.  Nicely done - many thanks

#10

The command line installer we use to install from Corona to Device is broken in iOS 11. Our engineers are looking into solutions. For now you would just either chose “Show in Finder” or “Do Nothing” and use Xcode’s Device’s window to install the app.

Rob

#11

Rob - Thanks for the prompt reply - I’ll try that out…Cheers - Dom

#12

i have the same trouble… hope it will quickly be fixed :frowning:

#13

Same issue here - any eta on a fix?

#14

Unfortunately we don’t have an ETA for this.  

#15

Same problem! I have subscribed to this topic for hopefully positive updates. 

#16

According to the release notes, we solved this in the latest daily build 3157.  Give that a try!

Rob

#17

Hurrah… back in business.  3157 works fine.  Nicely done - many thanks