parse-community / parse-community/parse-server-push-adapter
Push Notifications Stuck @ verbose: _PushStatus : sending push to 1 installations - but dont get delivered.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 96
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
Below is my code to send push notification , though it's success it doesnt get delivered to device.
Parse.Push.send({
where: {
"deviceType": {"$in": ["ios"]}
}, data: {
"title": "Registration",
"alert": "Push Notification working"
}
}, {
useMasterKey: true,
success: function() {
console.log("Push was Successful");
res.json("true")
},
error: function(error){
console.log(error)
}
});
Configuration:
var api = new ParseServer({
databaseURI: databaseUri || 'mongodb://localhost:27017/dev',
cloud: process.env.CLOUD_CODE_MAIN || __dirname + '/cloud/main.js',
appId: process.env.APP_ID || 'XXXX',
masterKey: process.env.MASTER_KEY || 'XXXX', //Add your master key here. Keep it secret!
serverURL: process.env.SERVER_URL || 'http://localhost:1337/parse', // Don't forget to change to https if needed
clientKey: process.env.CLIENT_KEY || 'XXXX',
liveQuery: {
classNames: ["Posts", "Comments"] // List of classes to support for query subscriptions
},
restAPIKey:"skillz",
verbose: true,
push: {
ios: {
pfx:'certs/services.p12',
topic: 'com.XXX.Skillz',
production:false,
passPhrase:'push'
}
}
});
Verbose Logs attached screenshot.
Any help is really appreciated.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Parse.Push.send call and the push.ios configuration shown in the issue, then inspect the verbose log attached to determine where delivery stops. Done means identifying a reproducible cause for the successful-but-undelivered notification and documenting or testing the resulting fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100