Andrew Bulat

Closing this issue as it has been inactive for more than a year. If you are still experiencing issues with using JWT tokens in ably-js, please open a new issue.

This has been implemented in ably-js v2 in https://github.com/ably/ably-js/pull/1645: PR removed `XHRStreaming` transport, replaced upgrade mechanism with a websocket + base fallback transport mechanism whereby no two transports may be...

Updating the suggested solution for this: You should add the next line to your next.config.js file: ```js const nextConfig = { // ... experimental: { serverComponentsExternalPackages: ['ably'], }, }; ```...

Closing this as the issue has been inactive for more than a year.

`updateStatus` returned by the `usePresence` hook has been updated to return Promise and be async. This change will be included in the next minor release for ably-js

Hello @bookercodes , @nikitadubyk ! Thank you for reporting this and providing steps to reproduce. We're going to investigate this and get back with an update as soon as possible!

Hey @bookercodes , @nikitadubyk ! I was able to reproduce the issue with the provided code sample. I'm currently looking into its cause.

Hey @bookercodes ! You are not doing anything wrong; this is an issue on the ably-js side. We're planning to release a fix for it this week. In the meantime,...

This has been fixed in https://github.com/ably/ably-js/pull/1761 and will be released in the next patch version for ably-js package.

Hey, the fix for this issue has been released in [2.1.0](https://github.com/ably/ably-js/releases/tag/2.1.0) release of `ably-js`. Thank you for reporting this issue!