IOS8 quick reply processing for push messages

http://blog.csdn.net/yujianxiang666/article/details/35260135

IOS8 has a new notification center with a new notification mechanism. When you receive a push at the top of the screen, you only need to pull down to see the quick-action interface, and you don't need to enter the app to operate. On the lock screen, the push item can also be processed quickly. Basically is to let the user try to do not leave the current page under the premise of processing push information, and improve processing efficiency.

The ability to interact directly with text messages, emails, calendars, reminders, and third-party apps allows you to quickly operate without getting into the program and focus on what you're doing.

• In the notification banner quick reply information, do not enter the SMS program;
• You can reject or accept email invitations directly;
• Reminders can be marked for completion or delay;
• When a third-party app updates the interface, it can quickly operate directly on the app.

Recently studied the official document of the next iOS8, the function is studied, basically the effect has come out. Because remote message push is cumbersome and requires background support, I use local push instead, basically they want to invoke the proxy method similar. Long story short, here's the basic process:

1. Create a message above the action to be added (the form of the button is displayed)

[OBJC]View PlainCopy 

2. Uimutableusernotificationaction *action = [[uimutableusernotificationaction alloc] init];
4. Action. identifier = @ "Action"; Flag of the button
6. Action. title=@ "Accept"; The caption of the button
8. Action. Activationmode = Uiusernotificationactivationmodeforeground; Start the program when clicked
10. //action.authenticationrequired = YES;
12. //action.destructive = YES;
16. uimutableusernotificationaction *action2 = [[Uimutableusernotificationaction alloc] init]; //second button
18. Action2. identifier = @ "Action2";
20. Action2. title=@ "Reject";
22. Action2. activationmode = Uiusernotificationactivationmodebackground; Do not start the program when clicked, in the background processing
24. Action. authenticationrequired = YES; It needs to be unlocked to process, if Action.activationmode = Uiusernotificationactivationmodeforeground, then this property is ignored;
26. Action. Destructive = YES;

2. Create a Category collection of actions (buttons)

[OBJC]View PlainCopy 

1. Uimutableusernotificationcategory *categorys = [[Uimutableusernotificationcategory alloc] init];
2. Categorys. identifier = @ "alert"; The only indication of this set of actions
3. [Categorys setactions:@[action,action2] forcontext: (Uiusernotificationactioncontextminimal)];

3. Create a uiusernotificationsettings and set the display class type of the message

[OBJC]View PlainCopy  

1. Uiusernotificationsettings *uns = [uiusernotificationsettings settingsfortypes: (uiusernotificationtypealert| uiusernotificationtypebadge|  Uiusernotificationtypesound) categories:[nsset Setwithobjects:categorys, nil Nil]];

4. Registration push

[OBJC]View PlainCopy  

2. [[UIApplication sharedapplication] registerusernotificationsettings:uns];
3. <pre name="code" class="OBJC" >[[uiapplication sharedapplication]   Registerforremotenotifications];

Userrequires call to Registerusernotificationsettings: silentinfo.plist uibackgroundmodes array contains Remote-notification? Can use both

Offline push packet with a specific category field (the field content needs to be defined together with the front and back table, must be consistent), when the phone receives, it can show the above code corresponding to the category Settings button, and Response button events.

Payload Example: {"APS": {"alert": "Incoming", "Sound": "Default", "badge": 1, "category": "Incomingcall"}}

Significant changes: The data can be brought up to 256 bytes before the offline push packet, and Apple now amplifies the value to 2KB. This is supposed to be for IOS8 only.

5. Initiating a local push message

[OBJC]View PlainCopy 

2. Uilocalnotification *notification = [[uilocalnotification alloc] init];
4. Notification. Firedate=[nsdate Datewithtimeintervalsincenow:5];
6. Notification. Timezone=[nstimezone Defaulttimezone];
8. Notification. alertbody=@ "Quick reply to test push";
10. Notification. Category = @ "alert";
12. [[UIApplication sharedapplication] schedulelocalnotification:notification];
16. //Use these two methods to determine if registration is successful
18. //NSLog (@ "currentusernotificationsettings =%@", [[UIApplication sharedapplication]  Currentusernotificationsettings]);
20. //[[uiapplication sharedapplication] isregisteredforremotenotifications];

6. Dealing with results in APPDELEGATE.M

[OBJC]View PlainCopy 

2. Local push Notifications
4. -(void) application: (uiapplication *) application didregisterusernotificationsettings: ( Uiusernotificationsettings *) notificationsettings
6. {
8. //successfully registered Registerusernotificationsettings: After the callback method
10. NSLog (@ "%@", notificationsettings);
12. }
16. -(void) application: (uiapplication *) application didreceivelocalnotification: (uilocalnotification *) Notification
18. {
20. //method called after local push message is received
22. NSLog (@ "%@", notification);
24. }
28. -(void) application: (uiapplication *) application handleactionwithidentifier: (nsstring *) identifier forlocalnotification: (uilocalnotification *) notification Completionhandler: (void (^) ()) Completionhandler
30. {
32. //In the non-user interface to receive local messages, the drop-down message will have a quick Reply button, click the button after the call method, according to identifier to determine which button to click, notification for the message content
34. NSLog (@ "%@----%@", identifier,notification);
36. Completionhandler (); //Finish processing the message, and finally make sure to call this code block
38. }
42. Remote push Notifications
44. -(void) application: (uiapplication *) application Didregisterforremotenotificationswithdevicetoken: ( NSData *) devicetoken
46. {
48. //Registered successfully with APNs, received the returned Devicetoken
50. }
54. -(void) application: (uiapplication *) application Didfailtoregisterforremotenotificationswitherror: ( nserror *) error
56. {
58. //Register failed to APNs, return error message
60. }
64. -(void) application: (uiapplication *) application didreceiveremotenotification: (nsdictionary *) UserInfo
66. {
68. //Receive remote push notification messages
70. }
74. -(void) application: (uiapplication *) application handleactionwithidentifier: (nsstring *) identifier  forremotenotification: (nsdictionary *) userInfo completionhandler: (void (^) ()) Completionhandler
76. {
78. //When the app is not launched, received the server push message, the drop-down message will have a quick Reply button, click the button after the method called, according to identifier to determine which button to click
80. }

After running to press SHIFT + command +h, to push the program to the background, or press Command+l to let the simulator lock screen, you will see the effect!

If the program is back in the background, after receiving the message, the drop-down message will appear the two buttons just added; if it is a lock screen, the left stroke will appear with the two buttons you just added.

The effect is as follows:

Now just can let the message show the form of the button, with the input box is still in the study, if you study out, also thank you can share Ah, we improve together!

Code: Https://github.com/ios44first/PushDemo

(If you want to reprint please specify address, thank http://blog.csdn.net/yujianxiang666/article/details/35260135)

IOS8 quick reply processing for push messages