2.1 App Store Release

What's New

Pro Upgrade

The new pro upgrade allows for logging in, replying to posts/comments, create new submissions, and to vote on posts/comments. The upgrade is a $0.99 in-app purchase, but if you were fortuitous enough, you could probably get it for free by building this app yourself. But ssshhhh, don't tell anyone.

Code Cleanup

Everything that was once in one giant ViewController is now in multiple VCs with a heavier reliance on the Navigation Controller scheme.

libHN

I created a library that I wanted to abstract all of the HackerNews API calls away from the app and make that more self-contained. That library is located here, and is also open-sourced for anyone to use in their iOS apps.

Version 2.0 Release to the App Store

• iOS 7 ready
• Filter by Top/Ask/New/Best/Jobs
• Show HN is in Orange
• Self posts now show up in the comments section

v1.2.3 Release - stable App Store build

• Pushed to App Store: August 4, 2013

What's Fixed

No More Crashing on Start! - It turns out, through my fiddling with iOS7, that I totally broke master. And as everyone knows, NEVER BREAK MASTER. Anyways, here's what happened: I put iOS7 beta on my phone and wanted to make News/YC look great on it (the status bar is funky), and in doing so, the XML of ViewController.xib was edited. I believe this slight edit was getting the .xib ready for the new OS - something Xcode asked me to do and I clicked yes. Well, I brought the same project back to Xcode 4.6, fixed the HTML entities that plagued the last release, and then submit it to the App Store. In doing so, I did another Developer no-no. I only tested in Debug. It worked fine in debug, but in release, it couldn't find the .xib file and crashed on start.

Basically, I messed up. I take all the blame on this one. However, I did find it odd that it somehow passed Apple's review process despite crashing on start every single time. Were they being lazy? I don't know. Just an interesting tidbit.

What's New

I added a #define to the HNSingleton class that determines if all of the changes to user management (logging in, voting, etc) that have slowly been built in should be activated or not. Just set #define kProfile YES if you want to edit any user functionality. I set it to NO right now for the release in the App Store until that functionality is solid (and tested in Release!).

HTML entities like #2x; and " should be good and fixed now. I couldn't get the NSString method for replacing escaped characters to actually work, so I hand coded those in. I'm not happy at all with that solution, and would love to get that handled.