141

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.

TheNeil
  • 3,321
  • 2
  • 27
  • 52
Dutchie432
  • 28,798
  • 20
  • 92
  • 109

6 Answers6

148

In Xcode < 4.0 (for Xcode >= 4, see answer by delirus below), 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

pkamb
  • 33,281
  • 23
  • 160
  • 191
Louis Gerbarg
  • 43,356
  • 8
  • 80
  • 90
  • 1
    Oh, one question though - my NSLog's dont seem to be printing...? – Dutchie432 Aug 06 '09 at 17:25
  • 19
    When you launch this way your application's stdin, stdout, stderr are not routed into GDB's console, they are pointed where they are in a normal app launch. You can see NSLog()s in the device's system console by looking at the device in the organizer. – Louis Gerbarg Aug 06 '09 at 17:35
125

For Xcode 4 you have to:

  1. Edit your active scheme via "Schemes" dropdown. (⌘+<)
  2. Than choose your product - 'Run MyApp.app' on the left.
  3. Select 'Info' tab on the right.
  4. And finally choose "Wait for MyApp.app to launch" option.

More here in "Customize Executables in the Scheme Editor" section.

EDIT:
In case you miss logs in GDB, see Louis Gerbarg's comment to his answer.

Community
  • 1
  • 1
matm
  • 7,059
  • 5
  • 36
  • 50
  • For those still having trouble finding the logs (like me), see owenfi's answer http://stackoverflow.com/a/25225961/1073754 – Eric D'Souza Mar 22 '15 at 16:29
116

For Xcode 10, 9, 8, 7 & 6:

  1. Select the Scheme on the toolbar (just left of the device you're debugging with)
  2. Choose Edit Scheme
  3. Select Run in the left panel
  4. For the Launch option, select Wait for executable to be launched
  5. Close the Scheme Editor and Run your Xcode project

Now you can debug when launching from a notification, custom url or by touching the app icon.

pkamb
  • 33,281
  • 23
  • 160
  • 191
bgolson
  • 3,460
  • 5
  • 24
  • 41
  • 10
    This answer caused me a lot of trouble even though it generally set me on the right path. Step 3 is a little bit misleading. You have to do it, of course; select Run in the left panel. But, there should also be a step 5 with very similar conceptual wording: Click xcode's Run button, before expecting the results... Since in the beginning it did not work for me, I asked for advice from other coworkers...they asked me if I did the Run thing, to which I replied yes, thinking of option no. 3... There should really, really, really be a step 5 to this... – Florin Odagiu Aug 09 '16 at 07:51
  • In case Xcode restores a different scheme tab, the Launch option is located under the Info tab. – Nate Whittaker Apr 17 '18 at 15:18
  • 9
    I'm not getting any output in the debugger window when I launch the app manually. – David Oct 07 '18 at 01:04
3

I'm not working with push notifications, so I don't know the exact working of push notifications. However, I'd try mimicking the receipt of a push notification by letting the main method of your program pretend a notification was posted if possible, or calling the application:didFinishLaunchingWithOptions: UIApplicationDelegate method from within the applicationDidFinishLaunching: method.

HTH - Cheers, Daan

drvdijk
  • 5,556
  • 2
  • 29
  • 48
3

In Xcode 6:

  1. connect iPhone to Macbook with USB
  2. launch the app on the iPhone by tapping the icon
  3. In Xcode menu, Debug > Attach to Process > Pick your App
Ali Saeed
  • 1,519
  • 1
  • 16
  • 23
2

For Xcode 11 and 10, you can do the following:

  1. Select Scheme option.

  2. Choose Edit Scheme.

  3. Select Run option from the left panel

  4. In the launch part, select wait for executable to be launched, then close the dialog.

  5. Build and run the project. You can now launch the app either by tapping the app icon, or by tapping on the notification message.

pkamb
  • 33,281
  • 23
  • 160
  • 191
Ramy Rizkalla
  • 164
  • 1
  • 7