#iOS and OSX Tips and Workarounds This document covers tips, tricks, and known workarounds for problems with the Cordova iOS platform or when building from OSX.
It covers the following issues:
- Errors about missing header or library files after adding a 3rd party Cordova plugin when building for iOS
- Permission errors from "npm" when trying to build on the remote agent, a CI server, or the command line
- Permission errors when building or executing a cordova command (plugin add) on OSX after checking in or copying the "platforms" folder from Windows
##Errors About Missing Header or Library Files in Plugins There are a small number of Cordova plugins that contain "custom framework" files for iOS which use symlinks on OSX. Symlinks can break when the plugin is either downloaded on Windows and then moved to an OSX machine or when the plugin is pulled from the Cordova plugin repo / npm without the symlinks being present in the archive as described in this Cordova bug. However, there is a simple hook that can be added to your project to work around this issue.
To install it:
- Download this hook-symlink-fix.js file and drop it a "hooks" folder in your project root
- Update config.xml with the following (using Right-Click > View Code):
<hook type="before_compile" src="hooks/hook-symlink-fix.js" />
- Run a "Clean" operation in VS or remove the ios platform and re-add if you are using the command line.
Alternativley you can install the Visual Studio Tools for Apache Cordova CLI Support Plugin which encapsulates this functionality.
##Permission Issues (EACCES Errors) ###Permission errors from "npm" when trying to build on the remote agent, a CI server, or the command line If you are seeing permission errors from "npm," you may be running into a situation where the your user's cache folder (~/.npm) is inaccessible. Generally this occurs if the folder or some of its contents was created while running as an administrator (sudo) when using older versions of Node.js and npm (though recent versions do not exhibit this behavior). Fortunately this is easy to resolve. Open the Terminal app and type:
sudo chown -R `whoami` ~/.npm
###Permission errors when building or executing a cordova command (plugin add) on OSX after checking in or copying the "platforms" folder from Windows If you are seeing errors that are originating from files in your project's "platforms" folder when building either Android or iOS on OSX, the root cause may be that you checked in shell scripts under the "platforms/android/cordova", "platforms/ios/cordova", "platforms/windows/cordova", or "platforms/wp8/cordova" folders from Windows. This is because the NTFS file system has no concept of an "execute bit" that is required to run these from OSX. (The contents of the platforms folder is generally not intended for checked in and by default are excluded from Cordova projects in Visual Studio as a result.)
For example, this error is saying the "version" script is not executable:
[17:41:57] Error:
/Users/vsoagent/vsoagent/agent/work/build/b424d56537be4854de825289f019285698609afddf826d5d1a185eb60b806e47/repo/tfs-vnext test/platforms/android/cordova/version:
Command failed with exit code EACCES
To resolve this problem you have two options:
-
Don't check in or copy the contents of the "platforms" folder. This is by far the path of least resistance.
-
If you absolutely must check in the contents of the platforms folder from Windows, you can craft a simple script to set the execute bits on these files and include it as a part of your build process.
-
Download this hook-execute-bit-fix.js file and drop it in a "hooks" folder in your project root.
-
Update config.xml with the following (using Right-Click > View Code):
<hook type="before_plugin_add" src="hooks/hook-execute-bit-fix.js" /> <hook type="after_platform_add" src="hooks/hook-execute-bit-fix.js" /> <hook type="before_prepare" src="hooks/hook-execute-bit-fix.js" />-
Commit / check these into source control.
-
Next time you build / run / add a plugin, the problem should be resolved.
-