parse-community / parse-community/parse-server-push-adapter
Status 400 and reason BadDeviceToken
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 96
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
I've updated the parse-server to the latest 2.5.3 version and parse-server-push-adapter v 2.0.0 and now my error logs are full of these messages:
3|parse-wr | node-pre-gyp
3|parse-wr |
3|parse-wr | ERR!
3|parse-wr |
3|parse-wr | parse-server-push-adapter APNS
3|parse-wr | APNS error transmitting to device 28c89bdc6a0e7a6454fb0cc446229a0841eecdea955533d3c549a658bb15fc98 with status 400 and reason BadDeviceToken
There are so many of them that I can't see anything else.
The questions are:
- How can I ignore these errors in my pm2 config file?
- Is there a way to remove bad device tokens automatically from Installation Collection?
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 APNS error path that emits BadDeviceToken and the PM2 configuration mentioned in the report. Check how invalid device tokens are represented in the Installation Collection; done means the requested logging behavior and automatic cleanup behavior are both clearly defined and validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100