-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected key "NSMainNibFile~ipad" while parsing error when installing the plugin for iOS platform #78
Comments
This did not work for me. I'm getting the same exact error when trying to install the braintree plugin. I installed plist before but it didnt help. This is preventing me from integrating braintree, any ideas? |
hmm. This Braintree plugin has not been updated/fixed for quite a while. I found one of the forks which has some fixes and used it - see #65
|
Is there any update on this issue @Taracque . I am facing this issue continuously on IOS while adding IOS using ionic Cordova platform add ios. This is blocking our production release. Do you have fix for this. Getting same issue - Unexpected key "NSMainNibFile~ipad" while parsing . as Braintree starts adding into the application and then it fails with this error. I tried with above solution and the repo, it starts giving some error in Xcode related to ENUMERATOR in TARGET section of the xcode. |
The error is as follows:
The problem is that one of the pre-requisites for this plugins is plist.js (https://github.com/TooTallNate/plist.js) and it has a bug when it incorrectly handles a empty string key, which causes this error - see TooTallNate/plist.js#79
This is not really the problem of this plugin but one of the dependencies. While there was a pull request to fix this (TooTallNate/plist.js#81) the problem still exists with the latest version of plist.
The temporary workaround is to install the plist from the fork where the fix is implemented https://github.com/akofman/plist.js
To install please run
This seems allowing to install the plugin without the above error
The text was updated successfully, but these errors were encountered: