Parse-server: GCM "upgraded" to FCM

[thailey01]

Please read the following instructions carefully.

Check out https://github.com/ParsePlatform/parse-server/issues/1271 for an ideal bug report.
The closer your issue report is to that one, the more likely we are to be able to help, and the more likely we will be to fix the issue quickly!

Many members of the community use Stack Overflow and Server Fault to ask questions.
Read through the existing questions or ask your own!

• Stack Overflow: http://stackoverflow.com/questions/tagged/parse.com
• Server Fault: https://serverfault.com/tags/parse

For database migration help, please file a bug report at https://parse.com/help#report

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!

• [ ] You've met the prerequisites: https://github.com/ParsePlatform/parse-server/wiki/Parse-Server-Guide#prerequisites.
• [ ] You're running the latest version of Parse Server: https://github.com/ParsePlatform/parse-server/releases
• [ ] You've searched through existing issues: https://github.com/ParsePlatform/Parse-Server/issues?utf8=%E2%9C%93&q=is%3Aissue Chances are that your issue has been reported or resolved before.
• [ ] You have filled out every section below. Issues without sufficient information are more likely to be closed.

Issue Description

[DELETE EVERYTHING ABOVE THIS LINE BEFORE SUBMITTING YOUR ISSUE]

Describe your issue in as much detail as possible.

[FILL THIS OUT]

Steps to reproduce

Please include a detailed list of steps that reproduce the issue. Include curl commands when applicable.

1. [FILL THIS OUT]
2. [FILL THIS OUT]
3. [FILL THIS OUT]

Expected Results

[FILL THIS OUT]

Actual Outcome

[FILL THIS OUT]

Environment Setup

• Server
  
  
  
  • parse-server version (Be specific! Don't say 'latest'.) : [FILL THIS OUT]
  
  
  • Operating System: [FILL THIS OUT]
  
  
  • Hardware: [FILL THIS OUT]
  
  
  • Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): [FILL THIS OUT]
  
  
• Database
  
  
  
  • MongoDB version: [FILL THIS OUT]
  
  
  • Storage engine: [FILL THIS OUT]
  
  
  • Hardware: [FILL THIS OUT]
  
  
  • Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): [FILL THIS OUT]
    
    

    Logs/Trace

  
  

You can turn on additional logging by configuring VERBOSE=1 in your environment.

[FILL THIS OUT]

[mruizkogi]

this will be fixed?

[lewellyn]

Apparently new GCM keys cannot be created. How does one integrate Parse Server with GCM/FCM now?

[thailey01]

Creating a project on the firebase console automatically creates the server
key and id you need. Just plug those in like you did with gcm

On Oct 10, 2016 4:21 PM, "Matt Lewandowsky" [email protected]
wrote:

Apparently new GCM keys cannot be created. How does one integrate Parse
Server with GCM/FCM now?

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ParsePlatform/parse-server/issues/2649#issuecomment-252749608,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFkyEsBfE6lH54IUgqAr7_L7riDX8Q4mks5qyqx0gaJpZM4J0Uon
.

[lewellyn]

Thanks. Will https://github.com/ParsePlatform/parse-server/wiki/Push be updated to reflect the FCM migration? Or is that a "patches welcome" thing? 😉

[hoang-ei]

@thailey01 Hi I've setup everything according to Firebase FCM guides. Than I set api key and sender id to my parse-server. But push notifications are not arriving to android. If I try to send push from firebase console it works correctly.

Can you please help me?

[thailey01]

There could be a few things wrong. I would need to see related code to get a better diagnosis but right off hand I would say to make sure you've followed the parse-server cloud code guide. Just from your description it sounds like the messages just aren't sending. Make sure you're sending pushes via cloud code as parse-server doesn't support client push. Be sure to add id to meta-data in your manifest.

[hoang-ei]

@thailey01 I use sashido.io seems it might be issues on their side. Since I am sending the push notifications from dashboard not from client.

[thailey01]

@hoang-ei Oh so you're saying you're sending pushes from shashido.io dashboard? I'm unfamiliar with this platform and so I couldn't tell you what is required for sending push notifications from them. However, if you are receiving pushes from the firebase console but not shashido I can only assume it is a problem with sashido.

[hoang-ei]

@thailey01 Yes I guess. Anyway I have one question for you, maybe this might be the reason. In your android project are you using firebase instance and messaging services or you are still using Parse broadcast receiver used with old GCM?

classes extending:
FirebaseInstanceIdService + FirebaseMessagingService
or
ParsePushBroadcastReceiver

[thailey01]

I'm still using ParsePushBroadcastReceiver.