Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 7 years ago.
Improve this question
I am using ionic to develop an app and everything had been working fine for some time.
However, I have recently updated to xcode 7.x so that I can compile for iOS 9. Now, when I run ionic prepare ios to generate the ios platform files and click on the *.xcodeproj file, I get the following error:
The file couldn't be opened.
The file can open just fine in xcode 6.x
I need it to work in xcode 7.x for the app to build with later SDK versions
Side note: I have searched for answers to this issue but in other cases the error message is more descriptive. The error message I get does not give a reason why it cannot be opened, be it permissions or parsing issues or otherwise, so I am stumped as to how to fix this. I have tried deleting (null) lines in files and deleting my <user>.xcuserdatad files as suggested in these answers anyway to no avail.
Cordova CLI: 5.4.1
Gulp version: CLI version 3.9.0
Gulp local: Local version 3.9.0
Ionic Version: 1.1.0
Ionic CLI Version: 1.7.12
Ionic App Lib Version: 0.6.5
ios-deploy-version: Not installed
ios-sim version: 5.0.4
OS: Mac OS X El Capitan
Node Version: v4.2.4
Xcode Version: Xcode 7.2 Build version 7C68
Question: why am I getting this error message and how I can fix it?
I have reinstalled El Capitan, xcode 7.2 and the necessary libraries (ionic, gulp, ..) and everything works fine now.
Curious...
I had the same problem, and it was caused by a different format of Xcode project file. If the project is compiled with the old Xcode, the new one cannot not open it.
I suggest you to remove any build file to make sure that next time project is really compiled, and if problem persist, remove also the old version of Xcode, because it looks like it is the one used to compile the project.
Alternatively, maybe ionic CLI has some option to select which Xcode it should use.
2 possible solutions:
1. Ionic configuration value
It seems that somewhere in your project, a config value makes ionic still think you use XCode 6 because you were using it before, and so continues to generate the project file accordingly.
What happens if you start over, in another directory, from a starter project file:
ionic start myApp tabs
ionic prepare ios
Can you open the generated XCode project file?
If yes, I suggest you to copy over this starter project all the files from your original project.
2. Update nodeJs to the latest version
I see you use node 4.x.x, try updating to 5.x.x.
I had something similar after updating Xcode, the git command line tool won't work after updating, turns out I had to open the Xcode and accept the license for new Xcode after that everything worked fine.
Related
I just started working on an already existing React-Native app that needs a really small update, but that has not been updated since October 2019.
The first thing I need, in order to start updating it, is to build the app. That is where I cannot find a way to do it.
At the moment, I’m trying to build the app only on iOS and not on Android.
First of all the current toolset versions I’m using are:
React-Native version: 0.53.3
Xcode version: 11.4.1
iOS SDK: 13.4
Node version: 8.16.6
NPM version: 6.14.1
I initially had problem with third-party tools, but I managed to fix it through manually installing them in the node-modules/react-native folder.
Now I’m getting errors about Xcode not finding headers of the modules the app is using
like, for example,
React/RCTViewManager.h file not found
Or, similarly, the GoogleSignIn.h headers in the RNGoogleSignIn module
I believe it’s just an error of how libraries are imported in Xcode, because as a test I have created a new react-native “test app” with the same exact versions of react-native and node, then I installed the core dependencies needed to perform the update on the original app, and I managed to build it without problems.
I’ve also tested building the app on an old Mac with macOS 10.14, using Xcode 9, but I’ve got different errors, always related to importing headers of modules.
This is the toolkits versions of the “old Mac”:
React-Native version: 0.53.3
Xcode version: 9.4.1
iOS SDK: 11.3
Node version: 8.16.6
NPM version: 6.14.1
Searching online I know that some of the problems I have faced (like the third-party react-native manual install) have been fixed in react-native updates, but I’m not expert enough with the technology to be sure that I can handle the update process without introducing bugs. I would prefer to just make this version run for now and facing the updating process later.
Do you have any suggestion of things about what I can do in order to successfully build the app?
If anyone ever comes here with a similar problem: the solution was pretty simple.
Be sure you're using the .xcworkspace file in your iOS folder, and not the .xcodeproj. This is used to automatically (and correctly) load the Pods dependencies in Xcode without having to manually link them.
Be sure that you installed the dependencies correctly with the right version of Cocoapods. We had to use an old version (1.5.x) that would automatically downloaded some pod dependencies. Our error was due to Facebook SDK. Newer versions of cocoapods did not download it, while the 1.5.x version would download it.
I'm building an ionic 2 app, and I can build the app with ionic build ios and I get no erros, but on xcode when I build my application I get the following error.
Apple Mach-O Linker (id) Error
Linker command failed with exit code 1 (use -v to see invocation).
How can I fix this?
Here is my system information
Cordova CLI: 6.5.0
Ionic Framework Version: 2.3.0
Ionic CLI Version: 2.2.2
Ionic App Lib Version: 2.2.1
Ionic App Scripts Version: 1.1.4
ios-deploy version: 1.9.0
OS: macOS Sierra
Node Version: v6.9.4
Xcode Version: Xcode 8.3 Build version 8E162
You are probably opening the .xcodeproj on Xcode, try opening the .xcworkspace. This fixed this error for me.
Had the same issue, spent almost a day trying to figure out what was causing it. For me the following solved it. Everything was working fine on ios#4.3.1, but on 4.5.3, I got this annoying error.
Check if this plugin "cordova-plugin-console" is there in the plugins folder. If it is there, remove it. Then it started building without any errors.
ionic cordova plugin remove cordova-plugin-console
Look for a file named libPods-AppName.a in Frameworks directory
where AppName is your app name.
Deleting it fixes it in most cases.
Take a look at the screenshot for reference.
Quick Fix
Disclaimer: My project uses Ionic v1
I had the same error and, once I had added a Android-only plugin, I thought that it was the cause of the error - I was wrong (so, ignore this cause if you think the same as I).
After some search I found the truly cause of the error: the cordova-ios version (4.5). I followed the steps suggested here and I solve this issue.
Steps:
ionic cordova platform remove ios
ionic cordova platform add ios#4.4.0
ionic cordova platform
Last step is used to check if ios#4.4.0 is actually the installed version.
Hope it helps.
In your platforms folder for ios, there are both .xcodeproj and .xcworkspace files. Open the /platforms/ios/.xcworkspace.
I found the issue that was causing this error.
On the config.xml file on the tag I had the email with my#email.com and you cannot have the .com on the email. I removed and it works fine now.
Thanks for the help
I have an iOS app that worked great in iOS 9 but when I upgraded to iOS 10, I am getting an error with alamofire. When I build the app it says
"Module file was created using an older version of the compiler, rebuild 'Alamofire' and try again"
I have attempted to rebuild it by typing carthage update and it does rebuild the framework files but when I re-add them as embedded or linked binaries, I get the same error. How can I go about diagnosing and fixing this issue? I suspect that this isn't an iOS 10 issue in particular but more just a rebuilding that I am failing to grasp.
Change Xcode's command line tools to point to the 8 beta app:
sudo xcode-select -s /Applications/Xcode-beta.app/Contents/Developer/
See the Swift 3.0 issue on the Alamofire repo for more info.
I am new to Cordova using Mac OS and I am just running the Mac OS in virtual machine.
Any help will be greatly appreciated.
When I build a project for iOS platform the build fail due to this error.
The plugin only installed is whitelist which require in new version of cordova.
Additional information may need:
- I am using Yosemite hackintosh.
- Cordova v.6.1.1.
- xcode 6.4
Thank you!
What's the version of your plugin of cordova-plugin-camera?
I sugest you
update Xcode from 6.4 to 7.0;
remove your dir, and create a Cordova project again.
then you can try "cordova build ios" again.
As you have installed only cordova whitelist plugin, this could not be a plugin issue. You can create a new project and port your code and try building iOS platform again. This solves the issue in most cases. Also ensure that you dont have any illegal or special characters in config.xml. Many a times, copy paste results in special characters addition in config.xml which causes this issue.
VS version - 2015 with Cordova update 3Mac OS - 10.10.4iOS - 9.0 When building in release mode for iOS we get following warnings. But release folder is created with ipa and plist.
So when uploading that ipa using application loader it gives following 2 errors.
As I mentioned in this stackoverflow thread:
There appears to be an issue with Cordova's iOS implementation when publishing apps created specifically using Xcode 7.
A Cordova community member has published a "cordova-plugin-ipad-multitasking" plugin with a fix.
http://npmjs.com/package/cordova-plugin-ipad-multitasking
Install this plugin and you should be all set. A future Cordova version will resolve the problem fully.
Failing that, if you are using remotebuild you can also find the native project under ~/.taco_home/remote-builds/taco-remote/builds and make the modifications as described in the Cordova bug on the issue.
EDIT:
To resolve ITMS-90339, there is a second step you can do to patch in the near term. Grab the build.xcconfig from the 3.9.x branch of the cordova-ios repo and place this under res/native/ios/cordova
Now remove this line:
CODE_SIGN_RESOURCE_RULES_PATH = $(SDKROOT)/ResourceRules.plist
Note that you will want to remove this custom build.xcconfig file if you upgrade to the version with the full patch that is forthcoming.