Florent Vilmart

@funkenstrahlen All good ! no problem!

@funkenstrahlen, does the error prevent any further notification being sent or will the connection be re established at one point? Asking that as we do not notice it and we’ee...

Yes indeed, can you open a PR for adding this error? On Sep 29, 2017, 1:04 PM -0400, bivisss , wrote: > 2.6.2 feature to remove invalid device tokens only...

you should set this in your environment variables, when starting your server. We'll make it the default on the next release.

Yes, it only removed the deviceToken from the DB, keeping the installations intact. As for the ping error, I’m not sure.

As we haven't seen much activity on node-apn and the never version is being actively worked upon, I tried a workaround (re-generate the provider at every calls) this may incur...

This is probably an issue with the node apn module, and therefore the push adapter

That’s quite unrelated, the emitter and leaks, but your call. 2.7.4 has been out for a while, and I’m not sure anything will be done in node apn for this...

Yep, and passing it into your ParseServer constructor, setting it in the package.json won’t automatically pick it up

@refre5h you can do it this way: ``` const pushOptions = { ios: {} // your iOS config } const { ParsePushAdapter } = require('@parse/push-adapter'); const pushAdapter = new ParsePushAdapter(pushOptions);...