* Hi - Please ignore this. There was nothing wrong with the file - it was very large and needed 30 mins to compile. Cheers! (That's what you get when you're used to small files)
I'm just a newbie and looking for some advice. I'm using Xcode 4.3.2.
Previously, I've had absolutely no problem archiving my projects and uploading them on the AppStore. Today, it's just not working and I don't even know where to start looking. I've changed no settings, and I tried another project and it archived just fine, so I'm assuming it's not my Xcode or any of my certificates.
When I tried to build the App, it just stopped on
"Compiling 9 o 9 source files... " and refused to go any further than that.
So I tried to Analyze the file, and it now hangs on:
"Generating dSYM file"
I'm obviously doing something stupid, and I don't even know where to go after this, and I have tried to google and everything else. I really would be grateful for any hints on where I could look or solve this.
If there's a Xcode developer in Perth, Western Australia - I'd be willing to pay for help because I'm that desperate. I'm not writing a killer App or anything like that, it's just that the whole thing is driving me nuts.
Cheers
Jacqueline
Related
Im running Xcode 9.2. My storyboards are completely useless now. Ive
experienced what this article shows and have tried everything the
article suggested.
My issue occurred when I tried to add a single swift file to an existing
objective C project with about 320 files in it already. I removed the
.swift file entirely from the project, then did everything in the article
link above and still nothing fixed it including removing/reloading XCode
several times trying different things.
I filed a bug with apple but haven't received any replies in a week (of course). Apple seems to be slammed with tons of bugs lately they keep
creating.
Now I cannot work on this project's storyboards at all and Im dead in the
water. Really not happy with Apple lately!
Is there anything more that anyone has had success in fixing this issue?
Im completely dead in the water on this application now.
Fixed this by setting the command line tools version to the correct one. Mine was blank in Preferences / Locations
For my case, whenever I open a storyboard from a workspace, this happens. So I got rid of cocoapods and workspace, then just use carthage for thirdparty libraries. Storyboards opens faster and without this error.
Note that the storyboard I am testing is empty.
This turned out to be stupidity on my part. I had a script that was killing certain processes on my Mac over and over and it turns out that was my issue. When I removed it everything worked as normal again.
I deleted the derived data and my frameworks are now messed up. Even though I removed and reinstalled the pod, xcworkspace simply refuses to detect it, worse it no longer creates the links and now it's all in red.
Really at a loss here.
Sorry if this seems like a stupid question but I'm self taught.
Latest update: I managed to get the app running again by changing "Build Active Architecture Only" from NO to YES. Not sure if this is the right way to do things but it works for me.
Still the frameworks are in red and I am worried Apple will not accept this project for it's store.
Anyone can help me with fixing it?
Progress # Day 2
I am trying to write a simple application trying to get my feet wet with VTK. Here is where I am so far. After searching for a while and attempting to download and build with CMAKE unsuccessfully, I found this blog from KitWare: https://blog.kitware.com/kitware-packages-on-os-x-with-homebrew/
So, I went off, installed homebrew, I believe "installed" VTK and Insight ToolKit. This was followed by self high-fives and all around self-congratulations. But.. I'm still not where I need to be.
I can't seem to sort out where to go from here. I believe I'm at the critical "now link the libraries with your project" state. I can find the installs under "/usr/local/cellar/Vtk/7.0.0_5/include/" and "/usr/local/cellar/Vtk/7.0.0_5/lib/" folders. The "include" folder has a bunch of ".h" files. The "lib" folder has a bunch of ".dylib" files. In a Xcode (V8.1) CoCoa Project, I've linked iokit, cocoa, and openGL frameworks and it builds. However, when I try to include something like "vtkActor.h", it fails to find it unless I specifically link that file.
Updated! Screen shot of search paths:
So, my questions are thus:
Am I actually done installing? I thought I was to end up with some ".a" files. Whats up with that?
If I am done, and I'm linked to all those .dylib files, why isn't it working? Should I link to all the ".h" files?
I've tried linking the folder "usr/local/cellar/vtk" folder, but it fails. Should I be doing that, but making it "recursive" I believe is the word.
Long run for a short slide... Anyone have any good tutorials/examples of a running Xcode OS X project so that I can get an idea how these libraries actually interact once I can even get them linked?
Thanks so much for your wisdom in advance. If anyone would have the kindness for mentorship off-stack until I can get up and running, I'd much appreciate it.
I've spent the past few months converting a project of mine with about 1500 source code files into Swift. It was incredibly tedious, but I finally did it. It runs well, builds well, but:
When I attempt to archive the project, Xcode fails with the following error:
ditto: can't get real path for source '/Users/USER/Library/Developer/Xcode/DerivedData/
APP-dtsbrzschafjiubelceuxtfwstqf/Build/Intermediates/ArchiveIntermediates/APPCore/
IntermediateBuildFilesPath/APPCore.build/Release/APPCore.build/Objects-normal/
x86_64/APPCore.swiftmodule''
Command /usr/bin/ditto failed with exit code 1
APP being the app and APPCore being the embedded framework.
What I've tried:
cleaning the project (which really has no effect when archiving, since archive always compiles from scratch)
using Xcode 7.2 beta (released a few days ago)
making as many declarations as possible non-public
disabling any Swift optimizations for the release build configuration
building the APPCore framework as release - which actually works (!) - and does (!) create the .swiftmodule file
The last part being the strangest here. This evidently points to the archive doing something slightly different, but I have no idea what.
My question is if anyone has any idea why is this happening and how to debug this. I've spent the last two days trying to figure this out, but no results...
I've googled this error as well, but unfortunately, the answers were fairly limited and suggesting to comment all lines of code and then start slowly uncommenting them until the project builds. Which is OK for a smaller project, but not for a 25KLOC project, mainly when you have absolutely no idea where to start...
I had the same issue and your question actually helped me to solve it (Xcode 8).
In debug mode just got the "ditto: can't get real path for source" without any further information. Switching to release mode showed me that the problem was that the framework wasn't allowed to have a bridging header file. I went to the build settings and removed the bridging header file (don't know why there was one) and it now compiles both in release and debug mode.
I've built and released a product for google play, I'm trying to release it to apple now. I've been following several guides through the long process but when I go to archive my product I get a lot of errors referring to Adbanners.
The most common one errors are Apple Mach-O Linker Error. I've been making apps for a year or so but this is my first attempt with Xcode so I'm probably overlooking something in the build settings or something but I've watched tutorials and searched the forums and I'm still stuck.
Thanks in advance for any feedback.
Figured it out. When I went to validate my project settings Xcode automatically selected the architecture for me which caused all the errors.
This link here helped me figure it out.
http://www.mobinett.com/2013/09/20/ios-7-xcode-5-project-build-settings-for-architectures-and-arm64-support/