Ios-deploy install fails

[RobertArissen]

Hello,

Expected behavior

Install ios-deploy global via NPM

Actual behavior.

Ios-deploy not installed and get the error:

Ld build/Release/ios-deploy normal x86_64
cd /usr/local/lib/node_modules/ios-deploy
export MACOSX_DEPLOYMENT_TARGET=10.8
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -arch x86_64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk -L/usr/local/lib/node_modules/ios-deploy/build/Release -F/usr/local/lib/node_modules/ios-deploy/build/Release -filelist /usr/local/lib/node_modules/ios-deploy/build/ios-deploy.build/Release/ios-deploy.build/Objects-normal/x86_64/ios-deploy.LinkFileList -mmacosx-version-min=10.8 -Xlinker -object_path_lto -Xlinker /usr/local/lib/node_modules/ios-deploy/build/ios-deploy.build/Release/ios-deploy.build/Objects-normal/x86_64/ios-deploy_lto.o -fobjc-arc -fobjc-link-runtime -framework MobileDevice -F/System/Library/PrivateFrameworks -framework Foundation -framework CoreFoundation -Xlinker -dependency_info -Xlinker /usr/local/lib/node_modules/ios-deploy/build/ios-deploy.build/Release/ios-deploy.build/Objects-normal/x86_64/ios-deploy_dependency_info.dat -o /usr/local/lib/node_modules/ios-deploy/build/Release/ios-deploy
ld: framework not found MobileDevice
clang: error: linker command failed with exit code 1 (use -v to see invocation)

** BUILD FAILED **

The following build commands failed:
Ld build/Release/ios-deploy normal x86_64
(1 failure)
npm ERR! code ELIFECYCLE
npm ERR! errno 65
npm ERR! ios-deploy@1.9.1 preinstall: ./src/scripts/check_reqs.js && xcodebuild
npm ERR! Exit status 65
npm ERR!
npm ERR! Failed at the ios-deploy@1.9.1 preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Steps to reproduce the problem

I only run the command: npm install -g ios-deploy

System Specs

• 1. system_profiler SPSoftwareDataType
  System Software Overview:
  System Version: macOS 10.12.6 (16G29)
  Kernel Version: Darwin 16.7.0
  Boot Volume: Macintosh HD
  Boot Mode: Normal
  Secure Virtual Memory: Enabled
  System Integrity Protection: Enabled
  Time since boot: 2:52

• 2. ios-deploy -V

• 3. xcodebuild -version
  Xcode 9.0
  Build version 9M202q

• 4. xcode-select --print-path
  /Applications/Xcode.app/Contents/Developer

• 5. gcc --version
  Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
  Apple LLVM version 9.0.0 (clang-900.0.34.1)
  Target: x86_64-apple-darwin16.7.0
  Thread model: posix
  InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

• 6. lldb --version
  lldb-900.0.41
  Swift-4.0

[shazron]

Hello, when you filed a new issue, you deleted the template of requirements needed for filing a bug report. Please do that, there is not enough information. Without it, this issue will be closed.

[RobertArissen]

Updated

[shazron]

This is the root of the problem:
ld: framework not found MobileDevice and you are using Xcode 9. It may be missing in Xcode 9. I will investigate later.

[DomT4]

It seems to have vanished from Xcode 9, but curiously is in the Command-Line Tools package Apple also distributes and after installing that it becomes available at the usual:

/System/Library/PrivateFrameworks/MobileDevice.framework/MobileDevice

Build still fails though.

[shazron]

It's probably looking for it at:
$XCODE/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/PrivateFrameworks/MobileDevice.framework/

where $XCODE is:
xcode-select -p

[shazron]

However, the linker does look for it at the location you found, see: https://github.com/phonegap/ios-deploy/blob/35c2c55fd15c3d20921941b44e3fd41b890f4253/ios-deploy.xcodeproj/project.pbxproj#L377-L380

[DomT4]

where $XCODE is: xcode-select -p

Yeah, this is enforced. If you flip it back to the CLT using sudo xcode-select --reset the build aborts & tells you your active developer path needs to be an Xcode instance.

This smells like an Xcode bug to me, I can't imagine why this behaviour would be intentional. If you create any small valid test.c file & then do:

~> clang -Wall -framework MobileDevice -F/System/Library/PrivateFrameworks test.c

It fails with the now rather familiar:

 "/Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld" -demangle -lto_library /Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/libLTO.dylib -no_deduplicate -dynamic -arch x86_64 -macosx_version_min 10.13.0 -syslibroot /Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk -o a.out -framework MobileDevice /var/folders/qs/rg1v7kz56wv3v9z4qwgtv3g80000gn/T/test-cfda58.o -L/usr/local/lib -lSystem /Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/9.0.0/lib/darwin/libclang_rt.osx.a -F/System/Library/PrivateFrameworks
ld: framework not found MobileDevice
clang: error: linker command failed with exit code 1 (use -v to see invocation)

But if you explicitly use the clang inside the CLT it works fine:

~> /Library/Developer/CommandLineTools/usr/bin/clang -Wall -framework MobileDevice -F/System/Library/PrivateFrameworks test.c

~> file a.out
a.out: Mach-O 64-bit executable x86_64

~> otool -L a.out
a.out:
	/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (compatibility version 1.0.0, current version 1.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.0.0)

~> ./a.out
testSUCCESS

[shazron]

Similar report in #311

[DomT4]

Apple is aware of the issue. Last update was 3 days ago, an acknowledgement that they are looking into it with the information provided.

[DomT4]

Apparently if some PrivateFramework linking remains broken through to GM we're stuck with it.

Apple took 10+ days to decide they had no interest in fixing the bug. So ios-deploy might continue to have issues with Xcode 9+ unless the Xcode clang is accidentally fixed or a workaround is found here.

I can link to other private frameworks just fine, so, I'm hoping they accidentally fix linking this specific one.

[antonioribeiro]

Trying to fix

For which updating header paths was not helping, I decided to install ios-deploy and now I'm getting the very same error and cordova build also gives me a

Error: ios-deploy was not found. Please download, build and install version 1.9.0 or greater from https://github.com/phonegap/ios-deploy into your path, or do 'npm install -g ios-deploy'

Thank you, Apple.

[DomT4]

Intentionally or not, this is apparently fixed in the Xcode GM. clang -Wall -framework MobileDevice -F/System/Library/PrivateFrameworks test.c now delivers success & the expected linkage.

[shazron]

That's great. We'll wait and see if it's permanent, the workaround should still work for now

[tommybananas]

@shazron what is the workaround?

[shazron]

@tommybananas see #314

[bjanuario]

If you are under Sierra you need to add the flag --unsafe-perm=true
sudo npm install -g ios-deploy --unsafe-perm=true

[tresdev]

@bjanuario this fixed the issue for me

[pyqui]

@bjanuario Oh yeah!!! It works!

[himalayaahuja]

@bjanuario It installs the package successfully yes, but again when I create a cordova ios build it throws the same error , saying ---------------
Unhandled promise rejection (rejection id: 1): ios-deploy was not found. Please download, build and install version 1.9.2 or greater from https://github.com/phonegap/ios-deploy into your path, or do 'npm install -g ios-deploy'

[pabloca88]

@bjanuario solved my issue.. great Job!

[mshyrokiy]

"sudo npm install -g ios-deploy --unsafe-perm=true" doesn't work for me
macOS 10.13.6
xcode Version 10.0 beta 3 (10L201y)

Is there any other way to get "ios-deploy" installed?

[sgalvagno]

@mshyrokiy
brew install ios-deploy

[ziwei3749]

@sgalvagno this way make it work,thx