First off, I realize there are a thousand questions with this subject, but I looked through many of them and could not find a solution.
I'm working on a simple tutorial from developer.apple.com. I have followed it step by step.
When I run the project, it compiles fine, but about 1 out of every 3 or 4 times the following happens:
As you can see I get no output in the console so I'm at a loss (99% of the other posts on this subject come with some sort of meaningful output). This EXACT same this was happening on the previous tutorial I worked on. I fixed it by deleting all localization files and turning off localization. Localization is not enabled on this project.
The connections for the IBOutlets are all fine. I tried adding an exception breakpoint, it doesn't trip.
I can post more information (source code, threads, etc), but I wanted to get a general feel as to whether or not it would even be valuable for the experts. The fact that there is no output might make it obvious. Let me know.
Thanks for your time.
As pointed out by Evan Mulawski and CodaFi in comments, this is a known bug:
Are you using OS X 10.8.4? If so, there is a bug in that update that affects the simulator. Use Edit Scheme and switch the debugger from LLDB to GDB.
http://www.tuaw.com/2013/06/05/devjuice-10-8-4-and-the-ios-simulator/
Related
I have recently updated to macOS 13.0 and for that minimum XCode Version required is 14.x series. But my existing project never getting successfully building. Its getting stuck at some point.
Its not getting failed. Build process screenshot is attached below. Its not pointing to any specific class. Seems like there are lots of classes which are getting compiled successfully at last but still build process is stuck at some point:
Seen similar threads like below on apple pages but nothing seems working. Does anyone got resolution?
Xcode 14 project compile error
XCode 14 compile errors immediately disappear or do not appear at all
Something similar has happened to me in the past on a number of occasions. If the Swift compiler is hanging mid-build, usually the issue is that there is some expression that is too complex for Swift to do the type inference on.
What you need to do is first find the exact statement that is causing the hang. This is how I do it:
First find out which source file is causing the problem. Look at the build log to figure this out (the build log can be located by looking at the reports navigator ⌘9 ). Find the build log and click on it. The build log will appear in an editor window.
One of the compiles will still be in progress and its file is the one you want.
The next thing to do is comment out all the code and recompile. This time the compilation will finish (if you have the right file, or there is only one) but probably with a lot of errors. Then you add the code back in, function by function, until one of them causes the compilation to hang again. If it's not obvious which line of the function is causing the problem, comment it out again and then add the lines back one by one until the compilation breaks again.
Once you have located the line, you need to simplify the type inference on that line. If it's a closure, try adding an explicit declaration for its parameters and return type. If it involves some complex array, try adding a type annotation to its declaration. Also try breaking down complex expressions into multiple simpler expressions.
There's no one size fits all answer to this but usually, once you have located the exact line that is causing the problem, it should be reasonably obvious how to fix it.
NOTE:
It has been a few days and I still am having this problem. One thing that would be helpful, is to know some troubleshooting ideas to try, so I can track down what is causing the crash. Any help that would lead me in the correct direction would be greatly appreciated.
I'm running in Xcode 8.2.1 on the simulator, as well as on several different iOS devices. I get the same problem wherever I go.
I have imported a small mp3 file into my spritekit project, called "cat_meow_1.mp3"
when I select the file, in Xcode, and hit the play button, it plays normally. Incidentally I have tried with various different files in various formats, with the same results.
in my code, which complies okay, when I get to the line:
run(SKAction.playSoundFileNamed("cat_meow_1.mp3", waitForCompletion: true))
I get a crash with the error message,
error: use of undeclared identifier '$r0'
Any suggestions how to debug this problem, or to figure out what I did wrong?
I also tried to preload the sound and make a class property, but got the same error. Here's what it looks like:
UPDATE:
After reinstalling Xcode, I still have the same problem. With certain files, I get white noise, while with other ones I get the error here. What else could be wrong with my system to cause this problem?
UPDATE 2:
tried my experiment on a separate mac, and basically it worked just fine. I reinstalled my OS, and got the same problem, with a little more of an error message this time, which reads:
2017-01-18 18:10:09.397565 sound attempt 2[533:124220] [DYMTLInitPlatform] platform initialization successful
2017-01-18 18:10:11.058506 sound attempt 2[533:124042] Metal GPU Frame Capture Enabled
2017-01-18 18:10:11.059146 sound attempt 2[533:124042] Metal API Validation Enabled
error: use of undeclared identifier '$r0'
warning: could not load any Objective-C class information. This will significantly reduce the quality of type information available.
After a couple days, I finally gave in and used Clean My Mac 3 to completely remove Xcode, as well as any and all related files... I must not have caught everything when previously I uninstalled/reinstalled it, because this time, there were none of my custom settings at all when I ran the reinstalled app.
It works now, thankfully, and I can get back to work.
I'm using AFNetworking to grab a JSON feed from our server and then I'm casting the response object that AFNetworking gives me into an NSArray, something I've done a million times before with no problem. The JSON is just an array with each element being a dictionary, nothing too complex.
The issue I'm having comes in when I set a breakpoint after I cast the response object to my NSArray. When the debugger pulls up, it shows the NSArray, shows that each object in the NSArray is an NSDictionary, but when I go to view the contents of the NSDictionary's, it will only displays the values and not the keys. The keys only appear as "(no summary)"
I've opened up the feed in my browser to double check it, and I used an online JSON validator to make sure the feed is valid and everything looks normal.
For what it's worth, this only started after I updated XCode to the most current version (7.3).
This problem is also affecting at least one coworker of mine, and he couldn't figure out how to fix it either. A fix to make XCode display the keys would be much appreciated.
Update
Almost three years and a new job later, I think I figured out why this was happening - though I can't confirm it since I no longer have access to the original project I was working on.
A few weeks ago I ran into this issue again - my debugger was telling me that some items were nil, gave 'no summary' on some dictionary keys, etc. It was driving me crazy.
The console gave me some hints as to what was going on by saying it was compiled with optimizations which may lead to debugger issues (or something along those lines) but that just led me to removing the optimization flags in the debugger. This just made my builds slow and did nothing to make my debugger act right.
As it turns out, at some point I had changed my scheme's build configuration from 'Debug' to 'Release'. In the 'Release' configuration symbolic debug information is not emitted and code execution is optimized - hence why the console was yelling at me that my code was compiled with optimizations and why my debugger was acting up.
Switching the Scheme's build configuration back to 'Debug' solved my issue.
While I don't know if this actually solves my original problem, it solved a similar one. Hopefully this will help others that stumble upon this question.
I have the same problem.
When I try debug with iPhone 5s Simulator, I see the same results as you:
But in iPhone 5 Simulator it is O.K :)
Try use another Simulator (5 or 4s)
Not sure what the problem is but I keep getting this error
Error creating files.
Stack dump: Compilation failed while executing : compile-abc
THATS IT! no explanation, no solution, searched online and all methods do absolutely nothing, I can remove large chunks of code and sometimes it works, its absolutely random when it works or doesnt work. Sometimes ill remove code and it will work and then I go to publish it again with no changes, AND IT DOESNT WORK!
My code is absolutely fine, it runs and publishes to any other format
Ive been at this for 18 hours and no sleep, Im on a deadline and I have to get this working , this is very serious, Adobe has really gone down hill
I have finally figured out exactly the cause of the issue.
Apparently packaging to iOS holds a hidden restriction,
functions appear to be limited to the amount of code they can contain.
This is not the case when publishing to anything not iOS related.
I receive this error when appending an already-successful build in XCode. What I don't understand is I'm not changing anything when appending, and this error shows up.
I've never used an 'old version of Xcode' as the error implicitly states.
Does anyone know how to get append working on a consistent basis?
This is a very simple project, and I'm using Playhaven and TapForTap SDK's, if that offers any insight.
Turns out, XCode upgraded itself without telling me. :(
I rolled back to the version I was using and all is well.
With no code snippets or error logs, it's very hard to determine what the source of your problem is. There's no way to know if your error is describing the cause of your problem or a symptom of the problem without more information.
I can only offer some suggestions:
My first thought is that you're using a deprecated method in your code somewhere, possibly "Append", which if that is the case, more than likely has an updated counterpart, but you'll have to check documentation regarding that.
If you've used "Append" previously with no errors, then you should look into what exactly you've changed in your new build, and verify that the methods you're using are supported.
If your errors are vague or unhelpful, you can begin the process of elimination and start commenting out blocks of code until it builds successfully, and narrow down the source of the problem significantly.
However, it would be to your benefit to expand your question with more information.