Package Revival - Firebase Cloud Messaging support #390
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.
This PR is based on #354 which was never merged. It's been manually rebased against the current master branch and updated for current-day compatibility.
The docs have been given a bit of a freshen up (I couldn't spend too much time here, they are still outdated in places).
Please review the documentation changes in the commit history for the full picture.
Notable changelog:
FCM Firebase Cloud Messaging support for both Android & iOS. New token type { fcm: }
BREAKING CHANGE: Meteor v2.14 is required (for Cordova compatibility)
BREAKING CHANGE: Push.Configure on the client now takes a cordovaOptions argument for configuration which is passed directly to cordova-plugin-push
BREAKING CHANGE: The Push.send argument android_channel_id has been renamed androidChannelId for consistency with other package argument names
Swapped out phonegap-plugin-push (deprecated) for @havesource/cordova-plugin-push
Added direct support for NotificationPriority / NotificationInterruptionLevel for Android and iOS respectively when sending via FCM, with the
androidPriority
andiosPriority
argumentsBumped cordova-plugin-device to v2.1.0 (previously 2.0.2)
This branch is currently in use in a production application, and I will be maintaining it in that respect for at least the next 2 years.
What needs to be done:
raix:push
package on Atmosphere? This will prevent a new release being published. Can install as a local package or git submodule until that's resolved.semantic-release-meteor
and manage assigning the version numbers manually.raix:eventstate
version to0.0.5
in your app's packages file. The latest published version has had all the code stripped out and just throws an error. That package ought to be un-deprecated and a new release published with versions 0.0.5's code restored.