Finally Done! ChronoCat 2.3 Submitted for Review

All right, ChronoCat 2.3 has finally been submitted for review. Here is the final list of all the new stuff it contains:

Add reminders to your events to let you know when they are approaching, the day of, or the anniversary of a past event 

You can now include a location with your events 

*Edit Events! 
Now you can edit an event after creating it 

*New look! 
The add event and view event screens have been given a new look and feel 

*New Help Section! 
There is now an FAQ section accessible via the settings menu with instructions on how to create events, delete events, and more 

Fewer 😀

ChronoCat 2.3, Still Coming Soon, I Assure You

Holy feature creep! ChronoCat 2.3 keeps getting bigger and bigger. Along with all the new changes mentioned in my previous post I have also finally added event editing. Reminders, locations, event names, dates, or photos can now all be changed after creation.  

This also means old events made pre-2.3 can be edited to include a location or reminder instead of having to delete and recreate them. Thank Kitty Pryde for sending my consciousness into the past and allowing me to prevent this dark future timeline from occurring. That future, one where events had to be deleted and remade to add a reminder or location instead of simply being edited, will now never happen.  

Anyway, just a bit more testing and 2.3 will be submitted to the App Store for review. With any luck it will be out sometime later this week 😀


ChronoCat 2.3 Coming Soon!

Huge update coming soon for ChronoCat, here is what is going to be included in version 2.3:

  • Reminders! Now you can add a push notification reminder when you create a new event.
  • Event Locations! Include a location with your events.
  • New look for the add event and view event screens including new date pickers and parallax event images!
  • Bug fixes!!!

Wow, so many exclamation points, I feel like Lewis Black telling jokes over here! 

How to Mess Up Your First In-App Purchase Submission

When adding an in-app purchase(IAP) to your app for the first time, be sure to follow the instructions provided by Apple closely. Make sure to dot your i’s and cross your… vision over the large warning at the top of the screen that says you must attach your first IAP to a new version of your app. This means it needs to be added after you create a new version in itunesconnect but _before_ you upload the binary for review. 

I thought the pending status on my IAP meant it would just automatically be reviewed with my app during its next update. Wrong! On top of that screwing up your first IAP is not grounds for an expedited review so will have to wait another full review cycle to fix your broken IAP (which was only about 4 days in my case so not a huge issue). In the interim I just threw a bug warning into my app’s “What’s new” section that IAP didn’t work and a fix was on the way. 

Here are some great articles from Apple that include step by step instructions on how to not mess your first IAP up like I did:
1. Adding In-App Purchase to your iOS and OS X Applications
2. Submitting your first in-app purchase product

How to Transition an Existing App to Core Data

The initial structure of my app ChronoCat was super simple: Just one custom class, all objects from that class are thrown into an array, that array is displayed by a table view and is written/read from disk as needed. Here is the basic process I used to migrate the app away from objects-in-an-array to Core Data:

  1. Make a Core Data entity to represent my custom class.
  2. Added all the @propertys from my custom class as attributes to the new entity. (@propertys only at this point, methods come later) .
  3. Make the NSManagedObject Subclass of my new Core Data model.
  4. Make a category for my NSManagedObject Subclass to store any methods I had in my custom class.

Now that the swap from a custom object to Core Data was complete the last step was to create a class to import the user’s existing data into the new Core Data model. Here is what I did for that:

  1. Made a new group in Xcode and added the old custom class used in the initial version of ChronoCat to it. The new version of my app is a complete rewrite so the old class file was not already in the project.
  2. In that same group I added a new class to put all my import code in.
  3. The import process is to check for the old data file in the app’s document folder, if found load the data from binary back into an NSArray, then use a for loop to cycle through the objects in the array and save them as a new NSManagedObjects.
  4. Once that’s done clean up by deleting the old data file.

The whole process was shockingly painless and has been a great way to get my feet wet with Core Data. The new version of ChronoCat that utilizes Core Data is currently in review and will hopefully be approved and available soon.

How to Add Device Frames to Your App Screenshots

I had always assumed the little iDevice frames you put your app screenshots in was done using Photoshop. I ended up happily being wrong on this one, there is a much easier way than Photoshop to do it. Instead of having to track down some Photoshop template and in my case, learn Photoshop, I was able to find a webpage to do it for me. 

The site is and all you have to do is pick your device, upload your screenshot, and it spits back out neatly framed in the device of your choosing. It’s what I ended up using for the new ChronoCat landing page, here are a couple of examples:

ChronoCat 2.0 Coming Soon

I am very excited to be finally submitting my 2.0 update for ChronoCat to Apple today!

This update includes a brand new interface and icon along with the ability to remove ads via an in-app purchase. A majority of the changes in this update are actually all under the hood changes that I will dive into more in a follow-up post. 

In the meantime, while I am waiting for Apple to approve the update, feel free to take a look at the new ChronoCat homepage to see how its going to look. 

ChronoCat Version 1.2 Now Available!

The latest update for ChronoCat is now available for download on the App Store! 

  • You can now share your events, including the photo and day count, to Twitter, Facebook, and more.
  • AirDrop support is also included so you can send pictures from your saved events to nearby friends. 


No Sound with AirPlay Extended Desktop on Mavericks

Been running into an annoying intermittent issue with AirPlay’s extended desktop feature where sound is not being played by the TV, it just continues to use the laptop’s built-in speakers. Restarting the laptop fixes the issue but that is annoying so after some digging I was able to find that the service “coreaudiod” is the one responsible streaming the sound (and possibly AirPlay all together, killing it breaks the connection to the Apple TV).

Just kill the coreaudiod process with Activity Monitor, restart AirPlay extended desktop, and that’s it, back to enjoying your talkies!