I always used to be able to see NSString values in the debugger, without problem. Since updating to 3.2.5 all I see is the format string {(char *)Xcode_CFStringSummary($VAR, $ID)}:s
I can't see anything wrong with that. Can anybody please tell me what the correct formatter should be?
I'm having this same problem and haven't found a solution. But at least I did figure out you can still view the strings by right clicking on the string variable and selecting "Print Description to Console".
I also had this problem and at the same time I noticed a couple of errors about missing symbols for xcode debug libraries (see here). Fixing the errors as described in the link also made my strings start working again. I realise you are talking about a different version of the SDK, but maybe the problem is the same.
Related
After a couple of times changing and saving a .cshtml file, the view starts to get frozen.
I recorded a video, you can check it right here.
Does anybody know how to solve it?
this is a known bug in VS for Mac and it will be fixed in an upcoming release. You'll need to update to the latest version (I'm not sure when that will be released, but hopefully soon).
Sorry for the inconvenience!
I am trying to build my first Unity 3D app to Xcode ever. I have tried looking at multiple different sources trying to make sure that I have all my settings correct, but for whatever reason I keep getting these errors in my Xcode workspace.
I have tried following these instructions from the Unity page to no avail. I feel like my problem is a common one that people face when first starting out. If someone could enlighten me to what I am doing wrong I would really appreciate it. Here is what my player setting looks like. Please let me know if there is another picture needed to figure out the problem. Thanks!
Good news! Those are not errors, those are warnings! Errors are red circles with exclamation points. GTMSessionFetcher is a "pod" - basically a plugin - so you can pretty much ignore those warnings, since that's not your code. The only warning you might want to look at is the top one, which is just Xcode encouraging you to update your project settings. Double click on that warning to get some suggestions on how to fix it.
Edit: you know I just now realized that Xcode error icons are octagons, not circles, like stop signs.
Various things are different in 1.0.136, e.g. running code with ctrl-enter has all sorts of strange behavior in an RMarkdown document, running code that has a syntax error somehow leads to all of the code being run in a block above (below?) the wrong code, etc. Sorry for not posting an MWE, but at the moment I just want to know if anyone is aware of these new "features" and if so how they can be turned off or better yet how I can just downgrade to the previous version of RStudio (which I can't currently find on the website).
Yes they changed some default settings that were present in the old interface.
Change the setting in markdown next to the knit button, from:
Chunk Output Inline -> Chunk Output in Console
Pictured here.
You can probably mess with the the Global Setting->Rmarkdowns under Tools to get it back the way it was before, but this was the fastest way for me.
When using App Code, autocomplete will only show results directly related to my struct. This is a great feature as it keeps everything very clean and I know that accessing these properties isn't going to give me an error.
Except I don't like App Code and it's non native looking UI.
In Xcode it's quite different. Why am I getting flatMap, map, description, debugDescription?
Obviously if its my own code, I know which properties/functions are okay to use, because I wrote them. I can just ignore the noise. But if I'm using someone else's library this can slow things down. Especially when I'm just guessing or trying to remember a function.
Is there a way to fix this — to have Xcode not show me functions/properties that I can't use?
It always shows default system objects properties if the object/class is not found.
It's the behavior of Xcode
I am trying to add custom fields to Phabricator, particularly Maniphest, and even the example given in the documentation does not work (there is an open quote in it, but even correcting that still does not help.
I have made sure that the config is a valid JSON, using Firefox's console and I have trimmed all tabs and spaces and yet it does not accept it. Any idea what am I doing wrong or if it is a bug? If so, is there a workaround?
I fixed the documentation. The example also had an incorrect trailing comma at the end. The best way to report bugs to us is to file them against the upstream, here:
https://secure.phabricator.com/maniphest/task/create/