Databases
StackOverflow2013
Postsdbo
POapplication:didFinishLaunchingWithOptions: firing notification before destination controller is created
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POapplication:didFinishLaunchingWithOptions: firing notification before destination controller is created
    primarykey
    data
    text
    <p>Hello, I am writing an app that should respond with an UI update and an internal status change when a local notifcation is used to open it. I am using storyboards and I have set up my main view controller to observe status changes:</p> <pre class="lang-objc prettyprint-override"><code>- (void)viewDidLoad { [super viewDidLoad]; // ... [[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(resumeByNotification:) name:@"Resume" object:nil]; } </code></pre> <p>In my app delegate I have this:</p> <pre class="lang-objc prettyprint-override"><code>- (void)application:(UIApplication *)application didReceiveLocalNotification:(UILocalNotification *)notification { if (application.applicationState == UIApplicationStateInactive) { [[NSNotificationCenter defaultCenter] postNotificationName:@"Resume" object:self userInfo:notification.userInfo]; } } </code></pre> <p>And this works just fine: if the app is running in the background, the view controller will intercept the notification and react accordingly. (If the app is running in the foreground, it's ignored because the UI is being taken care of directly.)</p> <p>The problem arises when the app has been killed and the notification is received. I have written this in the didFinishLaunchingWithOptions method, making the phone vibrate as a quick debug technique :), and I <em>do</em> get the notification:</p> <pre class="lang-objc prettyprint-override"><code>- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions { UILocalNotification *localNotification = launchOptions[UIApplicationLaunchOptionsLocalNotificationKey]; if (localNotification) { [[NSNotificationCenter defaultCenter] postNotificationName:@"Resume" object:self userInfo:localNotification.userInfo]; AudioServicesPlaySystemSound(kSystemSoundID_Vibrate); } return YES; } </code></pre> <p>The phone DOES vibrate so the notification IS there, but it doesn't seem to trigger the observer. I suppose that this is because the view controller's didViewLoad method hasn't been called yet. I am not sure how to work this around. I suppose I could use UIStoryboard's instantiateViewControllerWithIdentifier: method to make sure the view controller is actually there, but wouldn't I be getting an "extra" instance of it, in addition to the one that will eventually be instantiated by the storyboard's own life cycle? Judging from what the on the class reference documentation says, it's not exactly meant to do this kind of thing.</p> <p>Am I missing something very obvious here? In fact, is my approach the correct one for this kind of situation?</p> <p>Thanks!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USJollino
    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. VO
      singulars
      1. POapplication:didFinishLaunchingWithOptions: firing notification before destination controller is created
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POapplication:didFinishLaunchingWithOptions: firing notification before destination controller is created
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POapplication:didFinishLaunchingWithOptions: firing notification before destination controller is created
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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