Giters

braze-inc / braze-web-sdk

Public repo for the Braze Web SDK

Home Page:https://www.braze.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[Bug]: Safari push request didn't called

followthemoney1 opened this issue · comments

commented

deleted

commented

Hi @followthemoney1. The most common cause for this issue is an incorrect configuration in the Braze dashboard or a bad push certificate. I recommend that you reach out to our support team, as they'll be able to help you diagnose the issue more quickly.

commented

@followthemoney1 @wesleyorbin I have the same issues with Safari, more precise error is "Signature verification of push package failed"
Already regenerated certificate, it didn't help, also contacted support, they keep saying to read the docs

https://developer.apple.com/library/archive/documentation/NetworkingInternet/Conceptual/NotificationProgrammingGuideForWebsites/PushNotifications/PushNotifications.html

https://www.braze.com/docs/developer_guide/platform_integration_guides/web/push_notifications/integration/

Checked both, all looks good from my side

commented

My best guess that braze has some issues with package signing

As described here https://developer.apple.com/library/archive/documentation/NetworkingInternet/Conceptual/NotificationProgrammingGuideForWebsites/PushNotifications/PushNotifications.html#//apple_ref/doc/uid/TP40013225-CH3-SW10 package should be signed with both push certificate and intermediate certificate, and apple has new intermediate certificate as described here https://developer.apple.com/news/?id=jzd7wqva (https://www.apple.com/certificateauthority/AppleWWDRCAG4.cer)

commented

Ah, thank you for that thought @indy-dough, I think you're probably correct and I've filed an issue internally to investigate it from that angle, I'll reopen this and we'll report back with any subsequent findings

commented

Hi @indy-dough @followthemoney1. We updated the intermediate certificate on the backend. The workaround posted in #120 should now work. We will be releasing a fix for the baseUrl issue in 4.0 in the next few days.

commented

@wesleyorbin @froodian Thank you, it's working

commented

deleted

commented

Hi @followthemoney1. We released 4.0.3, which contains a fix for the baseUrl issue. Can you try upgrading to that version and see if the issue persists? If so, please reach out to our support team.

We've also released a feature to send users a push primer with no extra code required. If you open a support ticket, they will be able to enable that feature for you.