Databases
StackOverflow2013
Postsdbo
POhandling launching options and local notifications correctly
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POhandling launching options and local notifications correctly
    primarykey
    data
    text
    <p>I'm not absolotly sure about how to deal with the different states of handling a local notification (or a push for that matter).</p> <p>these are the different scenarios as far as I understand them (correct me if I'm wrong):</p> <p>a. app was in the foreground</p> <pre><code> - (void)application:(UIApplication *)application didReceiveLocalNotification:(UILocalNotification *)notification{} </code></pre> <p>is getting called and: application.applicationState == UIApplicationStateActive</p> <p>b. app was in the background</p> <pre><code> - (void)application:(UIApplication *)application didReceiveLocalNotification:(UILocalNotification *)notification{} </code></pre> <p>is getting called and: application.applicationState == UIApplicationStateInactive</p> <p>c. the app was terminated so:</p> <pre><code> - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions{} </code></pre> <p>is getting called first and afterwords:</p> <pre><code> - (void)application:(UIApplication *)application didReceiveLocalNotification:(UILocalNotification *)notification{} </code></pre> <p>is getting called where application.applicationState == UIApplicationStateActive (since it became active some time after didFinishLanching...</p> <p>In each of these 3 scenarios I should act differently:</p> <p>a. if the app was in the foreground, i would like to display an alert that shows the notificaiton body, and push some view controllers on the stack if the user dismisses the alert with a proceed button.</p> <p>b. if the app was in the background, and the user pressed on the alert then i would like to automatically push the view controllers to the stack, since the user's pressing on the alert indicates he wants to follow it's meaning.</p> <p>c. same scenarios as b. the user pressed on the alert and expects to see the relevant views.</p> <p>My Question is how/where should I push the relevant views to the navigationViewController and how to display the alert when receiving the notification in the foreground?</p> <p>The problem is that scenario c contains scenario a. this means, after didFinishlaunching got called (never mind if I handled the notification there or not) then didRecieveLocalNotification is getting called (as if I got the notification while in the foreground), but in this case i would not want to display an alert..</p> <p>Am I Wrong about the assumptions to begin with?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDavid Ben Ari
    1. USDavid Ben Ari
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COFor scenario C, `didReceiveLocalNotification` is not called, only `didFinishLaunchingWithOptions` is called. Since these are app delegate methods, they can receive the events at any time, and you can do anything you want from there. Maybe ask more specific questions, one at a time.
      singulars
      1. POhandling launching options and local notifications correctly
      1. USMarcus Adams
    2. CO@MarcusAdams, thx. I actually asked a very specific question, and followed it with wether I had my assumptions wrong to begin with. And I did, as you said the didReceiveLocalNotification method doesn't get called in scenario C, which simplifies everything. Go ahead and convert your comment to an answer and I'll accept it.
      singulars
      1. POhandling launching options and local notifications correctly
      1. USDavid Ben Ari
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload