My project was working fine in Xcode Version 6.1.1. I had upgraded the Xcode to 6.2 and tried to build the same project for iOS8. It gave me the following error :
Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/ibtool failed with exit code 255.
I had followed the suggestion given in the below link
Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/ibtool failed with exit code 255
Like :
a. deleted my app and restarted it
b. Cleaned the project and build
c. Checked for the xib file error
Still getting the same error.
But if I revert back to previous Xcode version it works fine.
Hi also Facing the same Issue:
Try This it will works for me:
Create a ZipFile of Project
when you close Xcode 6.1
Commit you Xcode Project..
When Open Xcode 6.2
Discard all the changes.
Run the Code.It will Work.
It is Xcode StoryBoard issue.
Related
I am using Xcode 11.0 beta and since two days I am stuck on this error. half of the project is built on SwiftUI.. I wonder if this is the reason that the error is coming...
I have tried restarting my Mac, deleting derived data, building and cleaning the project, updating the pods
I think think this problem is caused by SwiftUI
It usually tells you the reason when you click on it you can read about your problem , maybe a file is deleted or missing .
or if no logical reason was found , clean build your project it'll be ok . don't worry .
I update xcode version 9.4 to 10.2.1, I have created a project on xcode 9.4, run it once on xcode 10.2.1 and then delete this version and switch back to xcode 9.4 due to some reasons ... when I tried to run project on xcode 9.4 it gives lot of warnings and 198 errors
how to solve this issue.
If it's only linker errors, try to clear derived data on Xcode (Which you can access from Xcode > Preferences > Locations) and run application after clean and build. Some times your lesser disk spay might caused to these kind of issues as well.
When you opened the project on XCode 10.2.1 did you allow the project to be updated to the "recommended settings"?
It would have appeared as the yellow yield icon in the issues log.
A possible solution is to go into Time Machine (hopefully you keep backups) and revert your project folder to a copy from before you updated XCode
I am working with a swift project in Xcode 9. It was working fine and suddenly got some error while running.
Command/Applications/Xcode9.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc
failed with exit code 6
I have tried many ways such as Cleaning the project, delete derived data from Xcode and restarting the Xcode .
But nothing helped for me.
Now Xcode is quiting automatically at regular occations. I have created another test project. That too showing same issue
i was facing same error but i have installed Xcode 9.1 which has better performance and stable in compare to Xcode 9 .
My project works fine in Xcode 8.3.3. When I compile my project with Xcode 9, it shows compile error in some C++ files which have been included into my project for a long time. Then I switch to Xcode 8.3.3 and just want it built successfully, however, Xcode keeps on showing the previous error in Xcode 9.
Clean project/delete derived data/relaunch Xcode/reboot/uninstall Xcode9 and reinstall Xcode 8.3.3, all of them don't work. I think some of configurations are destroyed by Xcode9-beta2.
Anyone could help.
I'm having problems archiving an iOS Swift application since the last Xcode update (Xcode 7.3), the application builds and runs correctly in debug mode but as soon as I try to archive it I get the following error:
No such module "RealmSwift"
Although it references RealmSwift it fails randomly importing this or any other pod.
The most strange point is that downgrading to Xcode 7.2.1 and Command Line tools 7.2 doesn't fix the problem.
I've clean Cocoapods cache, completely removed ~/Library/Developer folder, removed my Pods folder within the project folder. Even trying to archive with a different machine doesn't work. I rolled back to a version of the app released on Crashlytics and therefore successfully archived in the past with the same result.
Any thoughts about what could be wrong?