New answers tagged

0

Right-click on a breakpoint Select "Edit breakpoint" Define an action


-1

Hope my experience will help, cause I've just went from confusion like you had to enjoying coding C on my MacBook in the past month. Need to give all the credits to the online resource where I learnt everything about setup the environment. http://c.learncodethehardway.org/book/index.html It taught me to just use the shell command through the Terminal ...


0

I had the same problem, and I found at the end that I had 2 simulator windows running at the same time. I close both of them and Xcode, and the problem was solved.I Had removed the simulator from dock preferences and run. I didn't need to restart my machine.


0

I reviewed /private/var/log/install.log to find the error and couldn't find one, so I removed it, and reran the install from the app store panel and it worked. Dunno what and if something else had changed.


0

Make sure your Mac OS is up to date. I was having these issues updating XCode and tried many of the solutions on this page, however, it took updating the OS to fix the issue.


2

This can happen with any app if you have formerly downloaded the same app (i.e. With the same internal "bundle id") from outside the App Store. Simply move the app to the Trash, restart the App Store app and try downloading the app again. Trashing an app does never make you lose your settings or even project. This is not Windows (where Uninstallers are ...


-1

Click the project on the lefts side.. General->deployment info change deployment target to 9.3 version...and archive the project and take ipa file once more and add ipa file to itune. hope this helps.thankz


1

Turn off the Show live issues checkbox in Xcode > Preferences > General (found near the top of the panel). I was experiencing the same issue. I found this answer through Editor glitch when editing near end of long file in Apple's Developer Forums. It worked for me running Xcode 7.3 with a 2706 line file. The glitch happened around line 2250.


0

In Xcode 7.3 it seems that you only have to unlock your device on the first build. After that, your device stays unlocked until you unplug it or exit the app you're testing.


0

If you've developer account, you can try to report the bug at  Bug Reporter with specific details of reproducing the issue. The time depends how on its Rank and whether the bug was described accurately. If it's major issue, I believe it'll get the response fairly quickly.


0

In the top bar: view->debug area->activate console


0

Make sure the Apple ID you're using is registered as an Apple Developer, XCode does not function with normal Apple IDs since they aren't linked to Apple's developer tools.


1

Yes I always found updating XCode from the AppStore a painful experience. Assuming you have a developer account, use this link and then find the version of XCode you need.


0

Silly me. I was having trouble adding my new account in Xcode. Once I did that, all was well.


0

I managed to get it working again by downgrading to version 7.2.1. Not ideal, but at least I can work now!


0

I'm an idiot, it can easily be disabled in the behaviors menu.


0

sudo rm -rf ~/.Trash/* is your friend. I would think cause of the errors are permissions, perhaps Xcode sets files with permissions exclusive to root (superuser). What sudo does is run the following command (rm -rf ~/.Trash/*) with root privileges - think of it as "when in doubt with permission denied, sudo". Of course, the permission denied error is not ...


0

Here's egold's ibeam solution updated for Xcode 7.3... https://github.com/ebaker355/better-xcode-ibeam-cursor Worked beautifully for me.


2

Here's the solution that works for me thanks to a github link provided by @aldryd. GitHub user sokobania provides the following steps: Step 1: Download ThemeEngine from: https://github.com/alexzielenski/ThemeEngine Step 2: Run ThemeEngine in Xcode and you may be presented with a few errors. Failed to code sign "ThemeEngine". Just click ...


3

It can be done using the ProjectWindowName Xcode plugin. You can install it via Alcatraz. Alcatraz is not officially supported, so sometimes plugins stop working after Xcode updates (reinstallation usually helps). Or some plugins might deactivate after an update, because the compatibility UUID for the new Xcode version is not listed among compatibility UUIDs ...


2

Simple answer is no. Swift (and objective C) is compiled into machine code and much od the naming is thrown away and optimisation will also alter the control structure. Experienced reverse engineers can get some form of code back but it is not very readable or useful in most cases. When you start any coding project the first thing you do is set up source ...



Top 50 recent answers are included