aboutsummaryrefslogtreecommitdiffhomepage
path: root/Firebase/Messaging/FIRMessagingRemoteNotificationsProxy.m
Commit message (Collapse)AuthorAge
* avoid calling [UIApplication sharedApplication] in app extensions (#1503)Gravatar Chen Liang2018-07-09
|
* Fix missing method in Messaging unswizzleGravatar Morgan Chen2018-06-29
|
* remove deprecated data message callback (#1068)Gravatar Chen Liang2018-04-11
| | | | | | * remove deprecated data message callback * Fix the issue that swizzling is not setup in recommended data message callback for message tracking.
* Add void's to eliminate Xcode 9.1 warnings (#352)Gravatar Paul Beusterien2017-10-09
|
* Don't swizzle missing and optional delegate methodsGravatar Riz2017-10-04
| | | | | | | | | FCM's swizzling of the user notification center currently swizzles only one of the two optional delegate methods (userNotificationCenter:willPresentNotification:withCompletionHandler:), but not the other (userNotificationCenter:didReceiveNotificationResponse:withCompletionHandler:). The didReceiveNotificationResponse, if implemented by the delegate, is the sole receiver of all user action on a notification, including simply tapping on the notification itself. Prior to this change, if the developer had implemented didReceiveNotificationResponse, then FCM would not be able to collect this event for analytics. Additionally, I changed the logic in FIRMessagingRemoteNotificationsProxy to check whether these methods are actually implemented before swizzling them. It was always swizzling, which meant it was adding an implementation if the method didn't exist. This would confuse iOS into thinking the developer did implement these methods and NOT fall back to delivering the notifications to the application delegate. With this change, if the developer did not implement these methods, then FCM will not swizzle those methods. That keeps the behavior true to what the developer intended.
* Log an error if for some reason we can't add a method to a class (#24)Gravatar Riz2017-05-23
| | | Maybe it was already swizzled, or some other issue. Either way, it would be good to log this error, as it might help us / developers diagnose an issue.
* InitialGravatar Paul Beusterien2017-05-15