This question already has answers here:
Hide strange unwanted Xcode logs
(14 answers)
Closed 6 years ago.
Has anybody else had issues with the Xcode 8 console showing a bunch of random stuff? I don't want to have all of this cluttering my debug messages and logs. Does anybody know how to turn this off?
EDIT: The release notes specify that the console might dump unhelpful stuff for watchOS, but not for iOS.
Example:
You can disable that output with a environment variable.
In Product>>Scheme>>Edit Scheme...>>Run add the following environment variable: Name:OS_ACTIVITY_MODE, Value: disable
Originally described on Twitter here.
It seems this information is not garbage and can help with the variables view when checking system framework calls. However, this seems more related to debugging for the engineers at Apple and seems to have been logged as an xcode 8 issue. No idea when this will be resolved.
I also checked (started) the key binding with a "show" and "display" filters but none are relative to this. Below is apple's note:
• Xcode Debug Console shows extra logging from system frameworks when debugging applications in the Simulator. (27331147, 26652255).
Related
For learning reason, I would like to get back the Master-Detail App template that was available in Xcode 11 and refer to the template codes inside. I also want both the Swift and Objective-C versions. However, to my astonishment it seems no one has asked this question before and seems there were no data source available where I could get back those files.
I try to reinstall my Xcode 12 back to Xcode 11 but that was not allowed as Mac complained that I am using Big Sur and I cannot use Xcode 11 with Big Sur. I also tried to check on YouTube etc. to look for potential useful information about Master Detail App and those existed on YouTube were from Xcode 5 or Xcode 6 or so where the split view controller thing were not in used yet.
I saw a reply online saying Master-Detail App is replaced with simply App and so we can just use App instead from there. That answer is of course factual but practically useless. As that answer assumed readers are pro enough to change between different templates, but if that's the case then readers like I won't need to ask that question in the first place. Readers look for that particular template for a reason, simply telling them to use something different is tautology.
In short, I cannot come up with a way to get back the exact Xcode 11 Master-Detail App template and I really need it for learning purpose. Is there something I can do with it?
You can search for tutorials (video or article) that uses Xcode 11 and get it from there.
My old iPad (ios9.3) refuses to load any reveal.js slides. It only shows the "Fork me on Github" image on the top corner. I suppose it will be that ios 9.3 does not support some new features of html5+js+css (I am not a developer, my skills are quite limited, so please excuse me if I say something stupid).
I am very interested in using it on an iPad due to the chalkboard plugin.
Any of you know what can be causing the trouble? Could I disable any of these features/files and make it work?
Thank you.
aimar
During all this weekend I was trying to figure out a solution. Finally, I manage to debug iOS safari from my windows laptop following this procedure and found that an "Unexpected identifier" was impeding "chalkboard" plugin to load.
A variable was defined with "let" command that, as I learnt, was not recognized by safari 9. I changed 4 "let"s with 4 "var"s commands in "plugin.js" (chalkboard plugin) and now it works in my old iPad, even with reveal v4.
Now I have another issue with the menus (menu plugin) not showing properly, but I will try also to fix it.
This question already has answers here:
Xcode keeps building storyboard after each keystroke
(2 answers)
Closed 5 years ago.
I'm using both Xcode 8.2.1 and when I write anything, even a single space, Xcode builds automatically the entire project, It's very annoying and make my Mac really slow I disabled "Live build" option in General setting, C language to compiler default in build phase but nothing changes. Any one know about it?
You need to disable "Automatically Refresh Views" from the Editor section.
It is happening because, as soon as you type anything, XCode refreshes the views as they might change due to any changes in code.
Follow this link Xcode keeps building storyboard after each keystroke
Did you try to disable Show Live Issues in Preference -> General already?
This question already has an answer here:
Xcode issue navigator : What two arrows blue icon mean?
(1 answer)
Closed 6 years ago.
Suddenly, I am seeing something very strange on my Xcode.
I realize that is a static analyzer to help me know where memory leaks can happen but I want to know now how to get rid of this and without changing my code. I mean., what configuration, I can change in xCode to remove that symbol as it wasn't there just minutes ago.
It means you have 72 "static analyzer warnings". The Xcode static analyzer parses your source code and tries to find things that you wouldn't want to happen at runtime (for example never releasing some object to reclaim its memory).
You can find a lot more about it here.
This question already has answers here:
SourceKitService Terminated
(34 answers)
Closed 8 years ago.
I have seen other questions with a similar problem but mine looks a bit more serious. Xcode keeps crashing on me. I have no chance to even edit a single character in my code. It is a very simple playground file with some basic code, nothing fancy. I'm not able to do anything at all in the current state.
When Xcode crashes, I hit reopen and the same thing happens again.
Locate the playground file using the Finder, then right click and select 'Show Package Content'. Next select the swift file, right click and open it using your favorite text editor (which must not be Xcode :)).
Once there, either delete its content or surround your code with comments. In the latter case, you can reopen the playground file in Xcode and selectively uncomment code line by line to know which line(s) cause Xcode to crash.
I've verified that there some recurrent patterns in code that almost always makes Xcode to crash, for example, when I use 2 or more custom operators in the same statement. I don't know if it that happens for all custom operators, or it's my specific implementation - either case, I know that I have to avoid that combination. You should take note when you notice a particular combination of code regularly making Xcode crash, and try to avoid it by splitting into multiply lines when possible.
Here's what I did to resolve it. I did reinstall Xcode a couple of times. It looks stable now but I'm not sure till when it would remain so. Looks like a bug to me. I will file it with Apple