You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FCM is swizzling both the methods of UNUserNotificationCenterDelegate i.e. willPresentNotification and didReceiveNotificationResponse. FIRMessagingRemoteNotificationsProxy.m
But while un-swizzling, only willPresentNotification method is un-swizzled and not didReceiveNotificationResponse. FIRMessagingRemoteNotificationsProxy.m
Due to this, the method didReceiveNotificationResponse of notificationDelegate class always points to FCM even after notificationDelegate is changed to a different instance. This creates a lot of issues when there are multiple SDKs swizzling these methods.
The text was updated successfully, but these errors were encountered:
I think this is the commit of interest 5496eff , PR #324 This commit added the support for didReceiveNotificationResponseSelector but missed it in the unswizzle part.
FCM is swizzling both the methods of UNUserNotificationCenterDelegate i.e. willPresentNotification and didReceiveNotificationResponse.
FIRMessagingRemoteNotificationsProxy.m
But while un-swizzling, only willPresentNotification method is un-swizzled and not didReceiveNotificationResponse.
FIRMessagingRemoteNotificationsProxy.m
Due to this, the method didReceiveNotificationResponse of notificationDelegate class always points to FCM even after notificationDelegate is changed to a different instance. This creates a lot of issues when there are multiple SDKs swizzling these methods.
The text was updated successfully, but these errors were encountered: