I am currently developing an app that receives Push Notifications. I have this all working 100% through a PHP page. There are several different types of push notifications my app can receive. The PHP handles this and sends different packets of information to my app which are all received just fine.
However, when the users "views" the notification and my app launches, I obviously want to take a different action than I would if the user just launched the app manually - and on top of that, different actions depending on the push notification type. I have got this working fine... structurally.
One of my push types is supposed to open a UIView that makes several connections to several different servers and negotiates data back and forth. This UIView works fine when, for example, triggered from the main menu - however when my push notification is triggering this UIView to appear, the socket connections are not acting as expected.
Now my question is not about the sockets, but more so - How do you debug such a problem?? From what I can tell (I am relatively new) when the app launched from a push notification there is no way to link that execution to the debugger / console / etc... I am having a very difficult time trying to debug the code using UIAlertViews, as there are many lines of communication back and forth between the various servers.
Any advice you have for me would be greatly appreciated.
SOLVED! Debugging App When Launched by Push Notification
I was able to get this helpful tip on StackOverflow.
Quote:
You can now configure Xcode to attach the debugger to the app after you launch it, instead of launching the app through the debugger. This lets you debug things that vary based on the launch state of your application, such as URL schemes, pasteboards, and push notifications.
1. In Xcode look in the Source bar, and below Targets there will be Executables.
2. Bring up the inspector for your app in executables.
3. Click on the Debugging tab tab in the inspector.
4. Uncheck "Start executable after starting debugger"
5. Check the "Wait for next launch/push notification"
Now when you click debug from Xcode instead of launching the app a window will display telling it is waiting for the app to launch. You then launch the app normally on the phone and Xcode attaches to it
I use two kinds of hacks for something like this. It's not for push notifications, but it's similar, because I was testing starting the app from an URL, which doesn't give me console output either.
1) On-screen output: This is similar to what you are doing. Instead of alerts, I am just putting a plain text label on the screen so I can see the outputs there. Limiting, and new text replaces old text, I know. But at least it's something.
2) Pretend to trigger an event: For example, I created a button just for debugging purposes. When the button is pressed, I manually call the method that normally handles the setups while started from other apps. This way, at least I get to see some console outputs out of it.
Haha, yeah, it would. We were writing those replies at around the same time. If I had seen your first, I would've probably thought "oh, that's a much better idea!" Hehe.