Currently, node-apn emits debug logs such as apn Ping response after 11.645432 ms.
This is ambiguous if more than one provider/client instances are created, e.g. when pushing to more than one app, or if refreshing credentials and creating a new Provider (exceedingly unlikely).
It may be useful to have a prefix that could be added to the passed in options to disambiguate them to see when something went wrong in a given client, e.g. here, it could be inferred that first-app stopped responding to pings
apn first-app: Ping response after 11 ms
apn second-app: Ping response after 12 ms
apn second-app: Ping response after 12 ms
apn second-app: Ping response after 12 ms
Low priority because reliability will hopefully be improved in the next release
Currently, node-apn emits debug logs such as
apn Ping response after 11.645432 ms.This is ambiguous if more than one provider/client instances are created, e.g. when pushing to more than one app, or if refreshing credentials and creating a new Provider (exceedingly unlikely).
It may be useful to have a prefix that could be added to the passed in options to disambiguate them to see when something went wrong in a given client, e.g. here, it could be inferred that first-app stopped responding to pings
Low priority because reliability will hopefully be improved in the next release