iTunes Connect now lets developers see crash reports

Apple has offered developers a glimpse as crash reporting since the iPhone 2.0 firmware was released, however, it was a kludge to get users to email you the crash reports from their ~/Library/Logs/CrashReporter/MobileDevice directory. Apple has a solution that will make this a lot easier.

Enter iTunes Connect, where Apple recently added the ability for developers to view crash reports from users. iTunes connect is where developers can manage applications they have on the App Store, check their sales, and get promotional codes for their apps. When you log into iTunes Connect you will be presented with the following information regarding crash logs:

Crash logs for applications are now available. To view them, go the Manage Your Applications Module below, click to view the desired application's details, then click View Crash Report.

When you navigate to Manage Your Applications > your app details > View Crash Report, you will be presented with a few items that could help you debug apps. Namely, developers can view most frequent crashes, timeouts, and memory usage right from iTunes Connect. You can find out more about crash logs on the iPhone by going to Apple's Developer tech note.

Starting out with Objective-C

I recently decided to embark on a personal challenge to learn Objective-C (the programming language behind Mac and iPhone applications) so that I could one day get applications into the App Store. I'm not looking to make millions with a fart machine app, but I do want to see some of my ideas come to fruition and end up on some iPhones. While we've previously mentioned how to delve into programming in Objective-C, there have been some recent releases of educational materials that can help those who want to learn the language:

Programming in Objective-C 2.0 (book, $44.99)

This is the latest release of Stephen Kochan's series which some consider to be the Objective-C bible. It has a wealth of information jammed into almost 600 pages, and it will take you from simple variable assignments to advanced class implementation. I'm over halfway through this book, and the text is easy to read (not too high level), and is broken up in a visually appealing style with sufficient whitespace to be gentle on your eyes. If you're only interested in programming for the iPhone, you may only want to rely on this book for its wealth of foundational Objective-C material as it only has one chapter devoted to the iPhone.

Learning Objective-C on the Mac/Beginning iPhone Development (books, $39.99 each)

This new series from Apress offers two options to would-be developers. If you're comfortable with Objective-C, grab their iPhone book and begin learning about the SDK and how to implement the iPhone features. If you're new to the language, pick up the first book to build a foundation so that if you decide to program for the iPhone, you'll be prepared.

Coding in Objective-C (screencasts, $5 per episode)

This is currently my favorite way to learn the language. While the company behind these high-quality screencasts, Pragmatic Programmers, has only released 2 episodes for Objective-C so far, they are a great way to learn thanks to the usage of audio and video. Being able to see the code change and grow and hearing the host's voice explain exactly what is going on is much more engaging than reading a book. The screencasts last about 45 minutes per episode.

These are only a few ways to learn Objective-C. Apple makes plenty of sample code available, and with the removal of the iPhone development NDA more and more blogs and books are coming available making it easier to learn and reducing the time to get creations finished. If you are already familiar with Object Oriented Programming (languages like Java and C++), learning Objective-C should be a snap.

Data loss from App Store updates [ MacOS]

When Apple first announced that third-party applications would be coming to the iPhone, they also announced an update mechanism in the App Store. On the surface, this ability to update applications (mostly for free) is a nice feature, however, when you learn that Apple didn't include a means for developers to save the data files created by their apps, you tend to start rethinking "nice feature."

I first noticed this when I updated Enigmo and lost all of my saved games. In addition, I just updated Facebook and lost my login information. Apple should have provided a way for applications to save information like this for retrieval after an update.

Have you encountered data loss in after updating your iPhone's third-party applications? Be sure to sound off in the comments.

Update: Judging from the comments to this entry this appears to happen on a case by case basis: sometimes updating an app will overwrite your data, other times it won't. Sure sounds like a bug to us! Though the question is: whose bug is it: Apple's or the 3rd party app dev's?