Certificate authentication disabled? about apn HOT 4 CLOSED

We switched the underlying library to pushok to support tokens as that seemed like the direction Apple was moving towards.

Is there a reason for staying on certificates, or just haven’t had a need to change?

You can keep using the version of the package you’re on, or override the service provider.

from apn.

Oh... I didn't do my research correctly. I can use version 0.6.0 and keep at upgrading Laravel (5.5 -> 6) in my project, and worry about the Token authentication later. I had version 0.2.0 in there, and I was a bit too eager to upgrade to the latest version of the library.

I'd rather not override the service provider because that sort of stuff has a habit of coming back to bite me somewhere down the road.

from apn.

I understand where you're coming from. If there was a common reason for people to continue using certificates we could update the service provider to bind against the AuthProviderInterface instead of the Token directly - which would give people the flexibility to pass in their Certificate credentials instead.

I'll close this for now but happy to revisit if necessary.

from apn.

I have just such a problem right now, I have a .pem certificate, and to send a notification I need to change the service provider (create a Сertificate instead of a Token). It will be great if you update

from apn.