We noticed players no longer registered for push notifications.
And apparently Apple changed the push notification token in iOS 13.
Instead of something like:
<124686a5 556a72ca d808f572 00c323b9 3eff9285 92445590 3225757d b83997ba>
It now returns:
{ length = 32, bytes = 0xd3d997af 967d1f43 b405374a 13394d2f ... 28f10282 14af515f }
Should we do a conversion from the client side or will Playfab update the backend to support the new format?
I see it's probably something that needs to change client-side.
Many SDK's apparently implemented it wrong.
More info:
https://onesignal.com/blog/ios-13-introduces-4-breaking-changes-to-notifications/
Under: Push Token Retrieval Changes
Hi,
So, the client-side must make some modifications to adapt the Push Token Retrieval Changes. Were you able to change the client-side and re-register those players for push notifications and get it working again? And, I also noticed that a new attribute is required on all APNS API headers, which might require some updates from PlayFab backend. I will inform the team to take a look at it, any updates will keep you informed.
We were using the Unity notification package and they just updated the package with the fix. We already tried the fix locally and it seems to work again!
Glad to hear that:) If you were to have any issues later on, please let us know:)
Update:
The issue that PlayFab backend may adapt to the change that a new attribute is required on all APNS API headers, here is possible work-around:
1) Use the "AdvancedPlatformData" push notification feature
2) Set the "SNS" "content-available" header
At the same time, the eg team is assessing this scenario and weigh in on whether it needs to be easier, any updates will keep you informed:)
2 People are following this question.
