APNs errors when using .p8 token

SSL Certificate Type
I understand that a .p12 certificate is scoped to a single bundle ID and environment. However, with a .p8 key, it is designed to be used by a developer account for all apps and environments. The Sendbird settings for managing the push notification certificate don’t give any guidance for whether a .p8 key should have the “Development” or “Production” SSL certificate type.

I was confused because the .p8 is ultimately a production value. However if you mark it as Production and use it to test sending a push with a token from a dev build, then it will return a “BadDeviceToken” error.

Question:
Am I correct in understanding that with a .p8 key, the “SSL certificate type” setting should depend on whether push notifications will target a production or development build? It seems to be working now that I changed it to “Development”.

(To help future readers, I also found this post which ran into the same errors as I am, though I’m using a .p8 instead of a .p12.)

Hello @Ben_Winters

Welcome to the Sendbird community!

Yes, you are correct in understanding that the “SSL certificate type” setting for a .p8 key should depend on whether push notifications will target a production or development build. If you mark it as “Production” and use it to test sending a push with a token from a development build, it will return a “BadDeviceToken” error.

Therefore, it is recommended to set the “SSL certificate type” to “Development” when using a .p8 key for testing purposes.

The post you found on the Sendbird community also confirms this issue and provides further information on resolving it.

Let me know if this helps in clarifying a few things here.