Logging suddenly stopped working in iOS app with xCode 4.6 - ios

I am using xCode 4.6. I upgraded when it first came out, with no problem.
Today, logging suddenly stopped working in my app. It has been logging no problem since I first created the app (years ago), then today it just stopped.
I have tried:
*Cleaning the project
*Deleting the derived data
*Closing and restarting xcode
*Deleting the app from the simulator
*Resetting the simulator
*Searching to see if NSLog (or DLog, as I am mostly using, though I do use some NSLog as well) was redefined somewhere (they weren't)
I have looked at other posts on this site, and they have not helped the solve the problem. I really do not know what to do from here.

You may need to choose Debug Configuration in Schema Info.

Related

React native release building at iOS error

Sorry, but I hate *pple. I have many reasons, and it is one of them. Debug version works fine even without any critical warnings, but release crashes at some screens
P.S.
XCode version 12.5
React-native 0.65.1
Step by step commenting and redeploying helped me to find the root of this trouble. Now, I know, but I can't understand why, you I can't pass custom methods to Array.prototype or Object.prototype. It worked with debug version without any troubles, but release didn't :(

Parse error "Could not build module 'UIKit'" but the app runs fine

I created a new project in Xcode 11, the "Single View app" in objective C. In every class the line #import <UIKit/UIKit.h> is highlighted in red, with the message "Could not build module 'UIKit.'" However the app builds and runs with no problem.
I've read a lot of questions like this on SO from years back, but none with XCode 11 and it doesn't sound like any of them would build without breaking. For me it is purely a parsing issue.
I tried deleting derived data, and I reinstalled XCode multiple times. The last time I went through this tutorial for completely erasing XCode from my computer: https://macpaw.com/how-to/uninstall-xcode-on-macos
Through the rest of the day the issue seemed to be gone. But this morning it's back again.
This seems to be happening with any XCode project I have, including brand new ones with no code changes.
I would just ignore the "errors" but it keeps me from being able to use autocomplete which slows down my workflow a lot.
Update
This issue seems to have gone away. I'm not sure why but I'm happy for it.
Update
This issue came back again after updating my computer. I have not been able to update Xcode for a while not. I'm not sure if the issue is related
Update
I was able to update Xcode, and the issue went away again.
I updated my Mac to Catalina 10.15.1 and was able to update Xcode to 11.2. After this the parse error discontinued and all of my syntax highlighting is back to normal.

Xcode 6.0.1 - iOS Simulator Black Screen

I've seen lots of questions about this - however none of them are solving my issue.
The Setup is as follows
OSX Mavericks 10.9.5
Xcode 6.0.1
iOS Simulator 8.0 (550.1)
I've tried now with 5 different Xcode projects, that are working with another machine with identical setups, except this one isn't working.
Every time I launch the simulator, whether or not it's with an App running, or standalone I get the same.
When I run from Xcode I get this message ->
An error was encountered while running (Domain = com.apple.CoreSimulator.SimError, Code = 146)
The things I've tried are:
Reset all Content and Settings (when I click and confirm this - nothing happens at all)
Removed all devices from the simulators, and re-created them
Made sure everything is up to date
Cleaned all projects, SEVERAL times
Restarted machine inbetween doing everything under the sun
Deleted Derived Data
This has been happening for 3 days now.
Suggestions please!
This probably isn't the "official" answer, but my solution to solve this was literally bin xcode, empty trash, then reinstall from the App store.
This post on the Apple Developer Forums has a bunch of highly relevant information. It doesn't appear to directly address your issue, but try this:
Turn up debug logging for the Simulator:
defaults write com.apple.iphonesimulator DebugLogging -bool YES
defaults write com.apple.CoreSimulator DebugLogging -bool YES
Quit and relaunch the iOS Simulator.
Check ~/Library/Logs/CoreSimulator/*.log for more information.

Xcode does not run the app on simulator. (App exited unexpectedly)

I'm developing for iPad (iOS 7), using Xcode 5.0.2.
Yesterday morning I was playing around with the app (my first app) and every time I ran it, it was displayed in the emulator perfectly. But after some 5/6 runs Xcode just stopped launching my app in the simulator. I started to receive this message:
MagazineManager exited unexpectedly - lost connection
Image:
I've been researching since yesterday morning for a solution with no luck. I even uninstalled and reinstalled Xcode, cleared the cache, delete folders... all that drama thinking it could be some sort of cache problem.
Then, going online I've tried lots of "solutions", none worked.
I've tried all listed here: Xcode suddenly stopped running project on hardware: "Could not launch xxx.app: .. No such file.."
and here:https://discussions.apple.com/message/23431537#23431537
and in more places.
After all my "try this, try that" I'm stuck with the same problem. I can only see a black screen at the simulator (image below) and that message at Xcode!
In my extensive research I've read that people are still able to debug using their iPad's. The problem is that I got the new iPad air, that's only getting here dec, 20th!! So I don't have a place to test my app[s].
Thanks!
UPDATE
Just got this message in the debugger console:
013-12-09 20:23:25.902 sim[607:303] /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/usr/bin/sim: Did not find an executable file at the path: '/Users//Library/Developer/Xcode/DerivedData/MagMan-bvhhiijesvrvuteunbmpsxcqgsst/Build/Products/Debug-iphonesimulator/MagMan.app'
My problem was the debugger. Actually, it still is.
The way I solved, and have been doing for every new project, was to disable the debugger and then run the project. That way I'm able to use the app on the simulator but without the debugging functionality.
I don't know what the problem is, what is causing this debugger issue in my case, but for now that's the best I could come up with. Thanks to the friends that replied to my question and helped my research I was able to test it and disable it.
This is how I disabled the debugger:
Project > Edit scheme
Set Debugger to None
If anyone knows a solution for this, feel free to answer this question and I'll make sure to update the selected answer accordingly.
Again, thanks for all your time and patience, specially #Popeye and #HotLicks that spent a lot of their time trying to help me.
Sometimes the simulator can be a bit flaky and just needs resetting. In the navigation bar at the top of the screen when the simulator is visible try:
iOS Simulator --> Reset Content and Settings...
This should reset all the settings and remove the content so all data, images, apps etc will be removed, its like it has never run before.
UPDATE
The answer on XCode5 can't install app on iOS simulator indicates the following
I found a "Fix" for this. After trying everything and getting the same error on "My App", I opened and tried to run "My App 2". "My App 2" ran fine, so I went back to "My App", tried again and this time everything worked fine. Crazy
If that doesn't work leave a comment and I will have another look.
Delete the app and restart your iPad it will work

iOS simulator not responding

Using both Xcode 4.4 and 4.5, I can't get the iOS simulator to actually start. It used to work, but one day it just stopped without any reason. I've tried reinstalling Xcode many times and rebooting, but to no avail. It just sits there bouncing away in the Dock, almost taunting me. Running my app on an actual iPad works fine, though. What could be causing this?
Here's the output I get from force closing it.
EDIT: it works now. The only thing I did was delete com.apple.finder.plist in ~/Library/Preferences to fix my Time Machine not working. Whether or not it was actually this that did it, I don't know, but it works now.

Resources