-
-
Notifications
You must be signed in to change notification settings - Fork 105
API Compatibility #246
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
API Compatibility #246
Conversation
Thanks for opening this pull request!
|
@charles-ramos I honestly do not have any opinion on this PR. Is this PR bringing in some previous functionality that was working before and is now broken? |
You can already use |
Hey @mman and @jimnor0xF, the idea is to keep everything compatible with the current code (GCM) that uses "data" for sending push notifications for Android. Right now, in case I want to send push notifications to everyone (android and iOS), I must use both "data" and "notification". With the PR I raised, it will be possible to keep using "data" for both. |
@charles-ramos Are you using Parse Android SDK to receive the notifications? If you do could you post a snippet of your broadcast receiver that handles receiving the push? |
@charles-ramos Back when we were using the Parse Android SDK we only used the |
Hi @mman and @jimnor0xF, I'm testing with the Javascript SDK.
With this PR, you can both send "notification" and "data" will work. Without that, the "data" will not work for FCM. Also, it will ensure that those who use the Parse Dashboard will be able to send push from there. It sends a notification as an "alert". |
@charles-ramos Could you please resolve the conflicts? |
With the latest release (version 6.2.0), everything covered by this PR is already working, so it's no longer required to proceed with it. Thank you everyone. |
Thanks for investigating |
New Pull Request Checklist
Issue Description
Adding API Compatibility, so he user can now send both 'notification' and 'data' as objects for push notifications for Android.
Additionally, adding compatibility with nested objects, so, JSON is now accepted and the same behaviors from GCM are now replicable for FCM push notifications.
Approach
TODOs before merging