
Check out this issue 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!
For implementation related questions or technical support, please refer to the Stack Overflow and Server Fault communities.
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!
How you managed to fix this? Because i have the same error, although 2 weeks ago i had no issue.
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
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 + '.');
});
Any news about this? I know the issue was closed but there are no solutions to be found...
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.
I actually solved this differently here:
https://github.com/parse-server-modules/parse-server-push-adapter/issues/35
Does the firebase solution require some different config or account settinga then the previous GCM config?
Most helpful comment
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.