Umair
Umair
Hi @sohamprodt, this seems to have been a stale issue from nearly 2 years ago. I'm not sure if we've made improvements in this area (the fact that you're also...
Closing due to inactivity. Please reach out if you're still having issues.
@lmars I'd assume so too with it failing to decode to json. This is the raw text printed out before it attempts to decode it: ```####### TEXT ��error��message�resource: invalid name...
@lmars I'm not sure I follow, are you implying the user is incorrectly assuming they will get a json response when instead it's actually a msgpack response?
That makes perfect sense - thanks @lmars! I'll get this prioritised in our next sprint planning
Hi @renbevz, would you be able to share some extended logs showing the "Disconnected to Ably!" output too please?
Apologies, I wasn't clear enough @renbevz. Could you send one long set of console output that includes the disconnected and message received logs. I have the same thought as @maratal...
Hey @renbevz, the issue lies in subscribing in the connected state case within the connection changed closure. This means you'd have N number of subscriptions (and printed messages) for the...