Add FCM push type and remove MPNS support due to its end of life #225
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
jguz-pubnub
force-pushed
the
feat/push-cleanup
branch
2 times, most recently
from
5c86617 to
3e88551
Compare
jguz-pubnub
force-pushed
the
feat/push-cleanup
branch
from
07a4512 to
b39dfd7
Compare
jguz-pubnub
force-pushed
the
feat/push-cleanup
branch
from
b39dfd7 to
c934bcc
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat(push): introduce FCM (Firebase Cloud Messaging) as a new push type option
feat(push): remove MPNS (Microsoft Push Notification Service) support following its end of life