Upgrading version 2.3.0 or 2.4.0 to 2.5.0

We did not release a template for 2.4.0, so this guide covers what you need to do from 2.3.0.

General updates

As Pugpig now supports a minimum of iOS 6, you may want to refactor your project to be more in line with iOS 7/ iOS 8 approaches. For the most part, this is optional. However, we recommend you do so to ensure that your app is not rejected by Apple.

  • Convert your old project to use ARC (if you haven't already done so). Xcode has an refactoring that will help with this - see the "Edit/Refactor/Convert to Objective C ARC" menu.
  • Update any deprecated rotation handling code (like shouldAutoRotateToInterfaceOrientation and didRotateFromInterfaceOrientation).
  • Update any deprecated UIViewController presentation calls (like presentModalViewController:animated:).
  • Optionally move your assets into an Asset Catalog.
  • Ensure that your build target is at least iOS 7, and ensure that your project is configured to build 64-bit architectures too.
  • Ensure that any layout code deals with the new device sizes (like the iPhone 6). Our default template now uses simplified xibs, with most of the UI elements laid out automatically.


We now support sharing using a UIActivityViewController. Further information can be found in our our 2.3 -> 2.4 upgrade guide.

Push Notifications

We now support a generic system for handling push notifications. Urban Airship is no longer our default push provider. More information is available in the 2.5 release notes. You must also ensure that you don't try to set badge numbers if the user doesn't grant the appropriate permissions. See the new template's AppDelegate for an example.

Background Transfers

If you want to support background downloads, you will need to add some additional code when updating. More information can be found here here.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk