Does stream support iOS 13 push notifications?

[getstream]

Does stream support iOS 13 push notifications?

[EJohnF]

Some my findings which might be helpfull:
I don't see in dashboard push notification logs the entities for Push notifications to ios 13 (no error, not row for this user)
And I made sure that this user is offline - I killed the app where he was logged.

[EJohnF]

from this issue: GetStream/stream-chat-swift#31

I tried to add "apns-push-type":"alert" to the template.

And now I see logs, but it says:

I thought it's because of the wrong key or team ID -> double-checked that it's correct

[bdandy]

Hi, @EJohnF, we are having support for new apns push type. It shoudn't be added to the template directly, it's done on backend side.

Are you using development or production push settings?

[EJohnF]

Hi @bogdan-d, thanks for looking up
okey, I've removed this field from the template

I'm uploading .p8 auth key -> which should work for both, development and productions
And the toggle in ios settings -> I tried in both states (on and off for development toggle)

for testing, I'm using AdHoc production build

One more I've noticed, that I'm receiving logs now, about the error during push sending, but the message is different within the same set-up (the app is killed, and certificates/settings are the same):

• publishing the message failed with error: BadDeviceToken
• publishing the message failed with error: InvalidProviderToken

[bdandy]

Hi @EJohnF

We are currently having the issue with p8 keys you are talking about, working on fix for that.
I recommend you temporary to use .p12 key instead.

Can you check push notifications are working now?

[EJohnF]

Hm, I did nothing special (all settings still the same, and still with p8 key) - and notification start to come on ios13 as expected :/

Seems the issue with p8 is resolved? Or I shouldn't rely on this way?

[bdandy]

Issue with p8 is different issue, not related to the topic.

Closing this one