Continue reading »]]>

The June issue of (IN)SECURE was recently released. I’m liking this magazine more and more, with straight, to-the-point articles and high quality content. In this issue:

• Becoming a computer forensic examiner, by Zeljka Zorz
• UEFI secure boot: Next generation booting or a controversial debate, by Aditya Balapure
• What startups can learn from enterprise level data security tactics, by Dr. Hyeyeon Ahn
• To hack back or not to hack back?, by Kai Roer
• DNS attachs on the rise: Rethink your security posture, by Srinivas Mantripragada
• IT security jobs: What’s in demand and how to meet it, by Mirko Zorz

Read Issue #38  (archived issues)

Sign up for their newsletter

Continue reading »]]> I’ve run into a recent issue where Xcode pins the CPU (technically it’s kernel_task) during a compile. Nothing major changed, so I tried clean builds, restarting Xcode, restarting OSX, but nothing changed. After a little bit of investigation, I found the culprit: I had a bad alias (pointed to itself or a nonexistent file), and it seemed like the compiler got stuck in a loop trying to resolve it. Once I fixed this and added that actual file back to the project, everything compiled fine.

Continue reading »]]> I came across an interesting issue this morning and I thought I would share. I was editing a ViewController and associated XIB file, adding an IBAction to do some (irrelevant) things, but nothing was working. The IBAction wasn’t being called at all (though the viewDidLoad function was). I checked and double-checked that the outlet was referenced from the XIB file, to no avail. I tried clean builds, restarted Xcode, and everything else I could think of.

Finally, I tried resetting the iOS Simulator.

Bingo! The application crashed with a “can’t find XIB file” error.

The problem was that after a git merge, the XIB file was removed from the target, and so wasn’t being included in the distribution. However, apparently since the old XIB file (without the IBAction) already existed, it was being used, despite a clean build occurring. I re-added the XIB file manually by choosing the Target, Build Phases, Copy Bundle Resources, and added the XIB file to that section. (I also had to add the associated implementation (.m) file to the Compile Sources section for a similar reason.)

I thought that when Xcode deployed to a simulator, it was transferring the entire application bundle, but it seems like it’s doing a (slightly broken) sync instead.

So lesson learned: If you’re troubleshooting iOS development and you ever don’t see your changes, you probably want to add Reset iOS Simulator Settings to your checklist.