Lawrence Forooghian

Hi @Mosquid, thanks for your report. It’s hard to know what’s causing this from the information that you’ve provided. My first question is whether you followed the [v2 migration guide](https://github.com/ably/ably-js/blob/main/docs/migration-guides/v2/lib.md)?...

Hi @Dajust, thanks for raising this issue. What environment are you running ably-js in? We've recently received a similar bug report for React Native (https://github.com/ably/ably-js/issues/1730). I think we didn't immediately...

Thanks for the confirmation. We’re working on a fix.

Fixed in #1640.

Hi @yibo-long, I'm taking a look into this issue. I can confirm that I've reproduced the behaviour you're seeing, when running in the iOS Simulator. It's worth mentioning here that...

> found .on function at channel level, and I think I made it work with following code: > > ``` > this.ably.connection.whenState('connected', () => { > const channel = this.ably?.channels.get(this.channelName...

> For 25s Transport Closed, I got logs from above code as: > > ``` > LOG AblyService: disconnected > LOG AblyService: attached to channel c:19523ec5747b400281f1d0c2dee2a391:5A989E2A-2179-4EC0-A120-E794D267ACE4 undefined > ``` I've...

Hi @yibo-long, do you still need help with this issue? I can post the example code that I was referring to in https://github.com/ably/ably-js/issues/1559#issuecomment-1908548893 if that would help (the problem that...

I was wondering what this proposal would mean for our existing [plugins mechanism](https://sdk.ably.com/builds/ably/specification/main/features/#PC1), which also aims to "avoid excessively bloating the client library". Might we wish to consider removing the...

I think that the proposal for splitting the library up into functional areas seems like a sensible one — the exact split I think depends on what our typical customer...