In an effort to better support our developers using open source and open standards, we are announcing that PubNub push notification event delivery is officially deprecated, and will no longer be supported starting March 31, 2024. Developers are asked to migrate their applications to Web Sockets before the deadline.
This will impact the following developers:
Developers directly using PubNub for event notifications
All developers utilizing RingCentral Embeddable to insert a web phone into a web page or application
How to migrate my application to WebSockets?
The steps every developer will need to take follow this simple recipe:
Login to the Developer Console, and edit your app's setting to add the "WebSocket Subscription" app scope to your application.
Upgrade your application to use the most recent version of the RingCentral SDK you have installed.
Make the necessary code changes. In most circumstances, only a few lines of code need to be modified.
Go back to the Developer Console and remove the "PubNub Subscription" scope from your application. This last step is important to signal to RingCentral that you have completed the migration process.
Please consult our WebSockets migration guide for code samples on how to migrate your app in each of our supported programming languages.
How to migrate RingCentral Embeddable to WebSockets?
RingCentral Embeddable is a toolkit that makes it easy to embed a Javascript web phone into any web page. RingCentral Embeddable is powered by PubNub behind the scenes and we do not recommend developers migrate Embeddable on their own. In the third-quarter of 2023, a new version of RingCentral Embeddable 2.0 will be released that will migrate your application to WebSockets and deliver a number of other new features and benefits as well. If you are a developer who uses RingCentral Embeddable stay tuned. We will work to make your upgrade process as smooth as possible.
Getting help and support
We recognize that changes like this have the potential to be very disruptive, and for that inconvenience, we apologize. We are committed to helping every developer make this transition successfully. If you need help, please consider posting your question on this post, or reach out directly to our developer support team.
Thank you, everyone, for your attention and for helping to make this change a successful one.
