Add IOS_FCM_ENABLED variable to allow disabling FCM functionality on iOS #797
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.
PR Type
What kind of change does this PR introduce?
PR Checklist
Please check your PR fulfills the following requirements:
New features/enhancements:
What is the purpose of this PR?
There is a conflict on iOS in case push notifications are handled by another plugin (Airship), i.e. when FCM functionality of the plugin is not used. Even with
FIREBASE_FCM_AUTOINIT_ENABLED
set tofalse
the plugin still would set its delegate forUNUserNotificationCenter
however preventing regular flow of notifications. This PR is allows to disable FCM on iOS viaIOS_FCM_ENABLED
variable.Does this PR introduce a breaking change?
What testing has been done on the changes in the PR?
Checked in an isolated example and used in a production app.
What testing has been done on existing functionality?
Other information