Xcode 6 won't build when I run simulator on mac or on my own ipad...
The last run in failed to build because of an error, which I fixed. Yet the error message, telling me that addObject is not a member, which clearly nonsensical, still remains in the code. I rewrote the code around the error and nothing is making it disappear, not restarting Xcode or my computer has helped either. I assume this has something to do with the crash.
Any idea what I can do?
For the error in the code, hit command+shift+k to clean your project. This might fix your problem.
If it still occurs, even after rebooting and restarting Xcode I'd recommend to reinstall Xcode completely: deinstall it first (using CleanMyMac for instance) and then download and install it.
Hope this helps :)
Related
Recently came onto this issue when trying to run my app on the simulator through xCode or the React Native CLI. The bundle loads from localhost then the app immediately crashes with "Thread 1: EXC_BAD_ACCESS (code=1, address=0x54)" in "main.m" in Xcode. I am unable to get the app running even though it builds fine. (even tried running on release instead of debug)
This issue just started recently occurring and I cannot find anything in our Git logs that would cause any kind of issue - all pretty minor changes on the RN side and nothing native. Has anyone seen this issue/knows how to properly trace it? Seems like a super generic error and it is unclear on how to figure out what is actually going on.
Xcode version 11.5, React Native 0.62.0, and targetting iOS 10.
EDIT:
After running the app a few times I was able to get this error in the Xcode Output
For me, running this watchman watch-del-all && yarn cache clean was what worked. I found it on an issue on github. Strange but it worked like magic
After tons of debugging, confusion, and many hours of frustration it came down to removing and readding one dependency. There was no specific error message I could trace or change I could find in our git history that would've caused this. I literally ended up tediously removing code from the App until I found the library that was the problem.
I'm getting an error Xcode 8.2.1 quit unexpectedly whenever Xcode is opened. This was working fine till last night. I have tried restart system but didn't worked.I have updated mac OS with macOS Sierra (version 10.12.3).
I already deleted derived data from preferences but it's not working for me.
please tell me why its happening like this...Thanks a lot in advance...
I've had this situation before.
My solution is that:
quit Xcode clearly
open other no question project or create a new project
open the your project again which will quit unexpectedly
it's maybe Xcode's bug, this is work to me, hope it's work to you too!
That state information might have become corrupted.
Follow these steps hope it will help you
1.) Right click on your project.
2.) Choose package content.
3.) Delete all extra files except project.pbxproj
4.) Come back to your project.
5.) Run
After using Xcode 7.2 beta, I turned back to my project in Xcode 7.1, and the app crashes on startup, I get this:
If i comment this line, I get a random error somewhere else. The app was working perfectly, I am sorry there isn't much to explain, but I really dont know whats causing this error.
I tried deleting Derived data and still the problem persists.
It seems like you have a breakpoint causing you some troubles.
Type "br del" in the console (lldb), type "Y" and enter to delete all breakpoints.
I am having a very big issue with Xcode 6. When there is a red error, it doesn't tell me what is causing it. It simply says red1, build failed, and when I press on the error I get redirected to Project -> general even if has nothing to do with that. When I get a line of code wrong, it does the same. It seems that my copy of Xcode has lost the ability to see errors. Furthermore just recently, my AppDelegate.m file has lost its "magic". When I edit it I do not get suggestions any more, neither errors. Has this happened to you?
PS: I have already tried restarting my mac and reinstalling Xcode.
As the title says, I'm having issues using LLDB. I've looked into this thread Xcode 4 hangs on attaching to (App name) when debugger is set to LLDB and followed the instructions given because I'm having exactly the same issue, and managed to debug by using GDB - it works flawlessly. Anyway, i'm working in a team and I'm the only one who's having this issue, so it's a bit annoying to switch back and forward from GDB to LLDB every time i commit changes so the workaround doesn't get synchronized in the remote repository.
I've checked the compiler, and it's set to LLVM 4.2. In fact, the app compiles perfectly and gets installed in the simulator (i can execute it once I kill and restart Xcode). I would try to reinstall Xcode, but it's a mess since it's a big-sized package and I have a limit on my internet usage, it would take a long while. Does anyone know what's happening here? Is it possible that LLGB is bundled outside XCode, even if I failed to locate it on the system?
Any insight would be appreciated. I can keep the workaround going, it's just that it's a bit annoying given my personal circumstances :-)
EDIT: More details about what I mean by 'hung'. I start with Xcode open, and simulator closed (it doesn't even appear on the Dock). I click 'Run', the simulator is launched successfully, and the application shows the Splash Screen. Then xcode shows the message: "Attaching to ". And now it's hung. You can close the simulator, and xcode is still attaching. Both the Run and Stop buttons stop working. You can try to exit the application by right-clicking on the dock, you get an alert message, and from this point you can't even type code: XCode is fully hung. The only choice here is to kill XCode by using Cmd+Alt+Esc.
This sounds like it could be the problem some folks were seeing in Why does the LLDB Debugger constantly fail to attach? where they'd modified their /etc/hosts file so when Xcode tried to connect to debugserver via "localhost", the connection was never set up.
When Xcode hangs, try switching to Simulator by clicking on its Dock icon. Don't use Cmd+Tab.
Upgrading to XCode 4.6.2 fixed this issue for me