-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: test multiple push event handlers in fcm sample app #274
chore: test multiple push event handlers in fcm sample app #274
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is identical in logic to the APN app. Same 3rd party SDK for local push, same callback methods added.
Apps/FCM/ios/Podfile
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only here for testing until the native iOS SDK goes to prod.
push: notification.payload | ||
}); | ||
|
||
completion({ alert: true, sound: true, badge: true }); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice that they cater the api level check themselves? 🤯
7a3868c
to
9e16474
Compare
Part of: https://linear.app/customerio/issue/MBL-383/[bug]-customer-unable-to-handle-push-notification-event-on-ios-with
Tests this iOS bug fix in FCM sample app, while also testing local push notifications in the app.
This PR:
AppDelegate
.After this PR, the FCM sample app will have 3 push event handlers: CIO SDK, rnfirebase, and the host iOS app (AppDelegate). This environment allows us to test the iOS bug that is caused when there are at least 2 push event handlers installed in an app.
Testing:
For all QA tests, we expect that both rnfirebase and the host app are able to handle the push events.