Was causing a warning with the -Wundef flag turned on when building the Mac project.
Vanilla iOS projects define DEBUG to be 1 in the Debug build configuration, and don't define DEBUG at all in the Release build configuration. That means that if you make a release build DEBUG is implicitly 0, but if you turn on the -Wundef warning flag you'll get warnings about this implicit value. This change explicitly makes sure both that DEBUG is defined and that its value evaluates to true.
…Path and APIMethod
Apple deprecated Gestalt in 10.8 without providing a sane alternative. I've implemented the current recommended approach to accomplish what Gestalt previously did (and thus eliminate my current project's annoying warning). Probably worth it to look into NSProcessInfo for 10.10+
…uld cause keychain keys to be in conflict Steps to reproduce: 1. Install a 3rd-party app with the Pocket SDK 2. Login 3. Build and run the test app under the Release configuration 4. The app should not be logged in, try to access other keychain items, or return a 137 error from the Pocket API
Reproducible steps: 1) Open the iOS test app 2) Login to Pocket 3) Approve access for the app 4) Get redirected back to the iOS test app 5) In the browser, go to getpocket.com/connected_accounts and remove access for the iOS test app. Do NOT log out within the app. 6) In the IOS test app, tap a row to save it. It will redirect you to auth again. 7) Tap "No Thanks" and get redirected back to the test app Prior to this commit, the test app would immediately try to log in again. Every time you tap "No thanks" it immediately attempts a new log in. With this commit, the test app would not try to log in again, and will correctly report an error.
Conflicts: Examples/MacApp/Mac Test App.xcodeproj/project.pbxproj