Conversation
Sample app builds 📱Below you will find the list of the latest versions of the sample apps. |
|
SDK binary size reports 📊SDK binary size of this PRSDK binary size diff report vs. main branch |
| didFailToRegisterForRemoteNotificationsWithError error: Error | ||
| ) { | ||
| MessagingPushAPN.shared.application(application, didFailToRegisterForRemoteNotificationsWithError: error) | ||
| } |
There was a problem hiding this comment.
I think maybe we can keep the names as they used to be to match AppDelegate callbacks:
- Make it less likely that people would be confused about their wiring
- It also future proofs our API in case we want it to do more than just registering/deleting token or smth else
| #selector(UIApplicationDelegate.application(_:didRegisterForRemoteNotificationsWithDeviceToken:)), | ||
| #selector(UIApplicationDelegate.application(_:didFailToRegisterForRemoteNotificationsWithError:)), | ||
| #selector(UIApplicationDelegate.application(_:continue:restorationHandler:)), | ||
| #selector(UIApplicationDelegate.application(_:open:options:)), |
There was a problem hiding this comment.
I believe we used to intercept couple of more App Delegate callbacks, do we need counterparts for these as well?
| } | ||
|
|
||
| @available(iOSApplicationExtension, unavailable) | ||
| open class CioProviderAgnosticAppDelegate: CioAppDelegateType, UNUserNotificationCenterDelegate { |
There was a problem hiding this comment.
I think we should deprecate this for the time being and have the two approaches live side by side. This gives customers more time to migrate since we have some time before app delegates go away
Complete each step to get your pull request merged in. Learn more about the workflow this project uses.