Can not start com.apple.debugserver on iOS 14 device under Xcode 12.0 beta 4

[albertdai]

MUST READ BEFORE YOU FILE (DELETE THIS SECTION BEFORE FILING)

Include the command line arguments you used for ios-deploy.

Don't forget to check out the README before filing this issue

The same thread in the libimobiledevice side: libimobiledevice/libimobiledevice#1004

Expected behavior

Install the app successfully and launch the app on the device

Actual behavior.

The command failed with "Error 0xe8000022: The service is invalid. AMDeviceSecureStartService(device, CFSTR("com.apple.debugserver"), NULL, &con)"

Steps to reproduce the problem

1. Connect to an iOS 14 device and use Xcode 12.0 beta4
2. Run ios-deploy -d -b {Bundle.app}

System Specs

macOS 15.5
Xcode 12.0
Build version 12A8179i

Please run the commands below in your Terminal.app and include it in the issue. Check when done and include results below.

• 1. system_profiler SPSoftwareDataType
• 2. ios-deploy -V
• 3. xcodebuild -version
• 4. xcode-select --print-path
• 5. gcc --version
• 6. lldb --version
• If using NodeJS/npm
  • 7. npm -v
  • 8. node -v

[gabebear]

I haven't tested beta4 yet, this may be related to #468

When Xcode12 hits GM I will look into this and #468 further.

[jmagman]

I'm also reproducing this on Xcode beta 5 (12A8189h). Right before reporting the 0xe8000022 error I see ImageMountFailed with underlying error Invalid value for MountPath

NSUnderlyingError=0x104404d10 {Error Domain=com.apple.MobileStorage.ErrorDomain Code=-2 "Invalid value for MountPath: Error Domain=com.apple.MobileStorage.ErrorDomain Code=-3 "A disk<…>

and the log is cut off.

Full log lines:

default	15:25:47.569886-0700	ios-deploy			mount_image (thread 0x10a321dc0): An error occured while sending message: ImageMountFailed (Error Domain=com.apple.MobileStorage.ErrorDomain Code=-2 "Failed to mount /private/var/run/mobile_image_mounter/25C675E46AAA49F25B2D1839230C980A65DFF73D19F9DE6CC597D02179EABC59DB2856C8014D23E7402D8E3D830119DE7D8C6C1B9859E44ED8551F6FD1F4196D/036753B3D2286FD3E3B196BA82B2F5FD7BFFAD7DD74681CE760D1C2B18A8F9729354CDAFE18ED016C92285DFE901E064A68C65A6D7F6DD1A7024C05A171FC15B/tFcvon.dmg." UserInfo={NSLocalizedDescription=Failed to mount /private/var/run/mobile_image_mounter/25C675E46AAA49F25B2D1839230C980A65DFF73D19F9DE6CC597D02179EABC59DB2856C8014D23E7402D8E3D830119DE7D8C6C1B9859E44ED8551F6FD1F4196D/036753B3D2286FD3E3B196BA82B2F5FD7BFFAD7DD74681CE760D1C2B18A8F9729354CDAFE18ED016C92285DFE901E064A68C65A6D7F6DD1A7024C05A171FC15B/tFcvon.dmg., NSUnderlyingError=0x104404d10 {Error Domain=com.apple.MobileStorage.ErrorDomain Code=-2 "Invalid value for MountPath: Error Domain=com.apple.MobileStorage.ErrorDomain Code=-3 "A disk<…>
default	15:25:47.569936-0700	ios-deploy			AMDeviceMountImage (thread 0x10a321dc0): Could not mount image: 0xe8000076 (kAMDMobileImageMounterImageMountFailed)
default	15:25:47.571077-0700	ios-deploy			hangup_with_image_mounter_service (thread 0x10a321dc0): Failed to send message: 0xe800002d (kAMDSendMessageError)

then:

default	15:25:48.586709-0700	ios-deploy			[ !! ] Error 0xe8000022: The service is invalid. AMDeviceSecureStartService(device, CFSTR("com.apple.debugserver"), NULL, &con)

[jmagman]

Looks like Facebook faced something similar:
facebook/idb@9743026

Error message is Error Domain=com.apple.MobileStorage.ErrorDomain Code=-3 "A disk image of type Developer/(null) is already mounted at /Developer." not sure what's up with that (null) or if it's the same thing here.

Their solution is to ignore 0xe8000076 error.

[jmagman]

Nope, nevermind that logging is benign, sorry for the noise

ios-deploy/src/ios-deploy/ios-deploy.m

Lines 617 to 619 in 89c509b

	} else if (result == 0xe8000076 /* already mounted */) {
	NSLogOut(@"[ 95%%] Developer disk image already mounted");
	} else {

[jmagman]

libimobiledevice/libimobiledevice#1004 (comment)

The problem is that the com.apple.debugserver service is no longer present as of Xcode 12 beta 4. The libimobiledevice code needs to use com.apple.debugserver.DVTSecureSocketProxy instead. (But it also needs to be smart enough to know which service to use, if you want to stay compatible with older iOS/Xcode versions. It seems that the "new" name also works with iOS 13, but I don't know how far back support for it goes.)

[albertdai]

The workaround/fix in libimobiledevice side could be replacing the service name com.apple.debugserver.DVTSecureSocketProxy and removing one line about SSL disable. See details in libimobiledevice/libimobiledevice#1004.

But I could confirm that only replacing the service name in ios-deploy could not fix the issue. May need more change same as the line about SSL in libimobiledevice

[xster]

Seems like https://github.com/libimobiledevice/libimobiledevice/pull/1012/files was a working solution for libimobiledevice. @gabebear would you be able to map it to ios-deploy?

[ivanhernandez13]

I took an initial look into this and I don't think that fix will map over to ios-deploy because that fix looks like it is done at a layer below where ios-deploy operates i.e. configuring and enabling SSL is done at the MobileDevice framework level.

ios-deploy might be able to drop down to that level to create and configure the connection to the device with SSL by following what other third_party tools do but i think the MobileDevice framework might already do this. I spent some time this morning into looking MobileDevice to see if there's something we're missing that tells it to establish an SSL connection with the device. Will look further in the next couple of days.

Been referencing this reimplementation of the framework: https://github.com/samdmarshall/SDMMobileDevice/blob/c3e1e97b1310c7a7a10f68281752760038b75e16/Framework/src/SDMMD_Connection.c#L194

[Ukalnins]

I created an pull request that should work. It would be nice to get some feedback if it also works for others.