Skip to main content

iPhone: Notification Center Trouble



I wrote an app that allows the user to enter data in a UITextField, and one of them allows them to enter in a specific date. I'm trying to have an alert appear in the iPhones Notification Center when the date is 15 hours away, even when the app is not running at all.





EDIT: New code-





- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions { UILocalNotification *localNotif = [[UILocalNotification alloc] init];







NSDateFormatter *dateFormatter = [[NSDateFormatter alloc] init];

[dateFormatter setDateFormat:@"MMdd"];

NSDate *eventDate=[dateFormatter dateFromString:eventDateField.text];



localNotif.fireDate = [eventDate dateByAddingTimeInterval:-15*60*60];

localNotif.timeZone = [NSTimeZone defaultTimeZone];





localNotif.alertBody = @"Event Tomorrow!";



localNotif.alertAction = @"Show me";



localNotif.soundName = UILocalNotificationDefaultSoundName;

localNotif.applicationIconBadgeNumber = 0;

[[UIApplication sharedApplication]presentLocalNotificationNow:localNotif];







}


Comments

  1. Store the date obtained from the text field in a NSDate object, eventDate. You will want to set the date with time also. The reason you are getting that error is that dateByAddingTimeInterval: should be called on an NSDate object and is not an identifier in itself. Set the fireDate of your local notification as

    localNotif.fireDate=[eventDate dateByAddingTimeInterval:-15*60*60];


    This will return a date which is 15 hours before the event.

    EDIT: You need to create an NSDateFormatter object and set its format to how it is stored in meetingDateField. Then use the dateFromString: to get the NSDate from the text field.

    NSDateFormatter *dateFormatter = [[NSDateFormatter alloc] init];
    [dateFormatter setDateFormat:@"mm'/'dd'/'yyyy"];
    NSDate *eventDate=[dateFormatter dateFromString:meetingDateField.text];

    ReplyDelete
  2. Youre trying to send the message dateByAddingTimeInterval: to whom? Nobody. You need a receiver for the message, an object that can then run the method.

    [[NSDate date] dateByAddingTimeInterval: -20*60];


    (NSDate date is the current date and time).

    ReplyDelete
  3. In order to call [-dateByAddingTimeInterval:], you must have an NSDate object. In your code above, you don't. It should look something like:

    NSDate* now = [NSDate date];
    localNotif.fireDate = [now dateByAddingTimeInterval:20*60];

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex