getting Error parse-server-push-adapter GCM send errored: 401 while sending push notifications  #1352

Activity

1. HemanParbhakar

   closed this as completedon Apr 4, 2016
2. kwstasna commented on Jun 15, 2016

   

   kwstasna

   on Jun 15, 2016

   More actions

   How you managed to fix this? Because i have the same error, although 2 weeks ago i had no issue.
3. HemanParbhakar commented on Jun 15, 2016

   

   HemanParbhakar

   on Jun 15, 2016

   Author

   More actions

   I have fixed it by changing the gcm key and could u show me the index.js file so that i could see the further error
4. alexfmadrigal commented on Jun 15, 2016

   

   alexfmadrigal

   on Jun 15, 2016

   Last edited by alexfmadrigal

   More actions

   I have the same error, my configuration is correct according to the documentation of parse, next to I put my code:

   var express = require('express');
   var ParseServer = require('parse-server').ParseServer;
   
   var app = express();
   
   // Specify the connection string for your mongodb database
   // and the location to your Parse cloud code
   var api = new ParseServer
   (
     {
       databaseURI: 'mongodb://localhost:27017/myapp',
       appId: 'tc',
       masterKey: 'master',
       clientKey: 'token',
       serverURL: 'http://localhost:1337/parse',
       push: 
       {
         android:
         {
           senderId: '1066279412344',
           apiKey: 'AIzaSyD2ysuFbFnNJNBwvILdemlxwf55q7yIHgI'
         }
       }
     }
   );
   
   // Serve the Parse API on the /parse URL prefix
   app.use('/parse', api);
   
   // Hello world
   app.get('/', function(req, res) {
     res.status(200).send('Express is running here.');
   });
   
   var port = process.env.PORT || 1337;
   app.listen(port, function() {
     console.log('Parse Server running on port ' + port + '.');
   });
   
5. DeDuckProject commented on Sep 13, 2016

   

   DeDuckProject

   on Sep 13, 2016

   More actions

   Any news about this? I know the issue was closed but there are no solutions to be found...
6. cagdasalagoz commented on Sep 16, 2016

   

   cagdasalagoz

   on Sep 16, 2016

   More actions

   I had the same problem. I found out that I should use the apiKey from Firebase. Not from console.developers. At your firebase account project settings > cloud messaging there you can find your apikey and senderid. Also don't forget to change it from your android/ios/js app or whatever is your client.

   👍React with 👍3Reacted by Jaime Agudo, Jared Alexander and Tanguy Vaessen

   😄React with 😄1Reacted by Tanguy Vaessen

   🎉React with 🎉1Reacted by Tanguy Vaessen

   ❤️React with ❤️1Reacted by Tanguy Vaessen
7. DeDuckProject commented on Sep 16, 2016

   

   DeDuckProject

   on Sep 16, 2016

   More actions

   I actually solved this differently here:
   parse-community/parse-server-push-adapter#35
   Does the firebase solution require some different config or account settinga then the previous GCM config?