I have tried deleting my derived data and restarting Xcode, and it works for a few seconds, until the Indexing is complete and then it's broken again.
Does anyone have any recommendations on how to fix this?
I searched in the apple developer forums and there are a lot of other users having the same issue. They say to go back to a previous version of Xcode 6 but I don't know where to find one, so any advice on that would be much appreciated as well.
I never realized how much I rely on Code Completion, I am pretty much stuck until I get this fixed.
PLEASE HELP!
This issue was resolved by upgrading to Xcode6.1.1
Related
This happens in the package manager console. What does the red text mean?
After I run the command, the migration file is generated, but it's empty.
I can't find an answer anywhere else. I'm very frustrated. I've done a research in google but that error happens in many situations different than this one.
The solution to this problem was to "downgrade" Entity Framework to 6.1.3. I guess the cause was a bug with the beta version. I was using: 6.2.0 beta.
Thank you guys for pointing this out! Thank you Gert Arnold. You rock!
The code just crashes when an already running particle effect's setVisible property is changed to NO, and later turned to YES. I have been working with ParticleEffects for a while now but never have I faced this error before. I don't know where I am going wrong. Its so frustrating. Please any help would do wonders. Im using cocos2d 2.x, xCode5 and well ofcourse Ive generated my ParticleEffects through ParticleDesigner. Hoping someone will help me out here.Thanks though :)
I ran into this issue also and found that it was a cocos2d bug. The fix was added here https://github.com/cocos2d/cocos2d-x/pull/6032/files and you can copy the changes if you don't want to update. (Seems to have worked well for me anyways.)
Trying to integrate my app with Facebook for login proposes, i've happened to notice the following log line:
2014-01-07 15:22:08.843 Nutrino[7457:70b] FBSDKLog: The FacebookSDKResources.bundle is no longer required for your application. It can be removed. After fixing this, you will need to Clean the project and then reset your simulator.
The problem is FacebookSDKResources.bundle is not even existing in my FacebookSDK directory. So basically this log message is redundant for me.
Normally i won't care much, but this log message is popping into my log console 3 times in a raw each time i'm instantiating FBLoginView.
Been looking around and saw this answer which state that the guy is probably getting this error after having upgraded to a newer version of Facebook SDK. Unfortunately i'm not upgrading. I started a new project from scratch so i don't have any reference to safely remove from the app project.
Any suggestions? How can i get rid of these annoying log messages
Thanks in advance.
Gil
UPDATE
Ok - I've found out the source of the problem!!
I'm developing my app in xCode5.. Once in a while I open an older version of xCode with an older version of the app for some code references, so the problem happens when both projects are opened simultaneously.
The FacebookSDKResources.bundle does exists on the older version of the project and this is the cause!
Hope it'll helps someone.
original answer
I'm not really sure if this is what solved it, since I left it as it was for a while and the next time I checked those log messages weren't there, but the only thing I do remember changing was the fact the I made my FBLoginView instance a singleton, so there was only one instance of it.
Worth the shot if anyone is dealing with the same issue.
I am currently attempting to port a game I've developed in the Wintermute Lite engine to iOS platforms. My game will compile just fine in XCode (albeit using the armv6 architecture) and will run perfectly on the iOS simulator; however, when I try to deploy it to an iPad, the first thread will halt in XCode with the error "EXC_BAD_ACCESS (code=1, adress=0xfffffff6)", pointing to a non-specific line of assembly code.
First of all, if you guys have any ideas right off the bat as to what might be causing this, I would greatly appreciate some help. The thing is, I'm more than willing to debug this myself, but being a complete noob with Objective-C as well as XCode, I'm not sure how to trace this specific error back to the line of code that's causing it (I apologize if this is a really basic question but I've already attempted to find a command to get the line of code associated with the error, but with no success).
I realize that this is scant on details, but as I said, I'm not sure how to pinpoint the piece of code that's causing this error using XCode, otherwise I'd just debug this myself. If there's any extra information I can provide, let me know.
Thanks in advance for any help!
I got it working. After a lot of messing around with XCode, I realized that I incorrectly configured the project file provided by Wintermute. As far as I can tell, it had something to do with the fact that the project was originally set to build for "iOS Universal" and I changed it to "iPad 5.0," which somehow caused the project to break upon deployment.
Anyway, I started over with a new XCode project file and got it to compile perfectly! Sorry for the bother.
The problem is the fact that it isnt ment to run on iOS. The reason it runs on he simulator is that it is building for a Intel chip set, not ARM. Even though you set it to armv6 it doesn't mean that the code will run on a non-intel device.
This should not create any Issues with the NDA as I am not asking anyone to reveal any functionality of the application, I have asked on the Developer Forums, but They dont have the user base or the response speed of StackOverflow.
I have been working with XCode for a while now. And other then these issues, I REALLY LIKE the new xcode. I will (when these issues are resolved) recommend this application to all iOS/OSX developers.
Anyhow.
I am currently developing iOS applications. And am Running this setup on Mac OSX 10.7.1 (Lion)
Issue 1:
If I use the Interface builder it will first of all stay open even after I navigate away from it and it is no longer visible or to my knowledge "running". After a while it will consume more then 4 gigs of active memory. I will have the activity monitor open and Will eventually have less than 20megs left of free memory. I upgraded my MacMini to 8 Gigs of memory and at this point it will get down to about 200 Megs of memory left and will eventually release the memory that IB had held onto. If I do not open IB in XCode 4 it tends to use a lot less memory. (adding 8 gigs of memory makes this memory leak a lot less of a problem)
Issue 2: (MOST ANNOYING, HOPING FOR A FIX TO THIS ONE MOST)
This one only currently happens on one of the Three machines I code on. And what happens is while programming if I [Run] the app it will work for a while. Then at some point through the process it will begin to Lock Up when I press Run or Command-R. If I save the code file and run. It will not lock up. However if I forget to save, It will not only lock up. But will force me to terminate the XCode app, and Subsequently Recode everything that I had edited since the last save and the Application Run. This is by far the most annoying bug I have encountered this far.
Issue 3:
This bug happens more and more often the longer the application and operating system has been running. Running into the iPad will give me a number of Errors including "Unable to Connect to Debugger" or "Finished Successfully" among others. But the important part of this issue is that the application will never get sent to the iOS device. It will compile and say it finished. But there will be a error in the output pane.
I hope others have encountered these errors and Hopefully there is a quick fix with config files or something that will make development a lot more convenient. Thanks to anyone for resolution to any of these issues.....
EDIT
I finally received an email from apple support. I have emailed them off a Capture from XCode 4 and will hopefully hear something from them. Or maybe they will just release a new beta. Either way I hope to get this resolved asap.
For issue #2 you might want to try auto-saving your code before runs. See XCODE auto save code when build and run? instructions. Not sure if these instructions will work for 4.2 but you get the idea.
I had issues with my Xcode 4.2 install crashing initially. Re-running the installer over the already installed Xcode 4.2 fixed them. Obviously I don't know what the underlying issue with the install was, but although the first install reported installation was successful, obviously it wasn't. Perhaps worth trying.
When a newer version of Xcode 4.2 becomes available to you (cough), you might want to see whether installing that one fixes the problem. Perhaps given the issues, you should try uninstalling the previous version first rather than installing over the top?
Do you use multiple windows? They are anathema to Xcode 4. If you persist in your heresy, it may corrupt some files, and slow itself down. You will see a lot of beachballing, and it will be in some sort of GC.
You can work around this by deleting a workspace-specific file hidden inside your project. (I will have to look up which one, if this describes your case.)
With the new Beta GM Release they have seemingly fixed the issue with the Hanging.
Thanks for the Answers. Ill +1 anyone who helped but ultimately it was apple that fixed the issue.... For now