Janison Sivarajah

> Hi @jsonsivar i have made the test case which is working fine on my system but tests are failing here on these automated tests on github I think it's...

Hi @talentlessguy , could you try this without the `endpoint: 'wss://auth-dev.space.storage'` and let us know how that goes? The value you currently have is a development sandbox and the problem...

Hi @talentlessguy , I wasn't able to replicate this in my node environment. I realized you are on Node 16 so I will try upgrading to that and see if...

@talentlessguy. I was able to reproduce this. The confusion was that our integration tests actually simulate the browser environment and so the SDK has only been tested and supported in...

Yeah @talentlessguy , looks like there is an issue with that and I don't think it was there before the upgrade. In order to merge this change you'd have to...

Hi @jordanlesich - this seems to be an issue with the `TextDecoder` not being polyfilled in properly. Can you try with the latest version of CRA? Our engineers @ChriLnth and...

I added this snippet in a local project and it seemed to have cleared the manifest file: ``` exports.onPostBuild = async ({ reporter }) => { // replace prefix paths...

Thanks @carsonfarmer! One small point of clarification, this error seemed to be slightly different from the one we get if the node is down. For that we get `Response closed...

So looks like blocking port 4006 didn't prevent the same error from happening again so the theory that it might have been due to network load is gone. It's happening...

Just to add more info, today we got the error on a `threadsClient.create` create as well so it wasn't limited to `threadsClient.find`.