Jeremy Meng

@CodeJuggernaut it looks like there's some internal limitation of around 2000 messages that we can handle before they are processed (complete/abandan/defer/deadleter). I will try to find out more but as...

@CodeJuggernaut just an update that this is actually a known issue https://github.com/Azure/azure-sdk-for-js/issues/11633. While we are working on a solution. I wonder whether the above workaround would work for you?

@zfyseu is it possible for you to try the other mentioned workaround of processing at most 2000 messages in a batch?

@zfyseu ah sorry I thought you were having the batching issue. Is it possible for you to turn on more detailed logging and share the logs when the SDK stops...

@zfyseu Thank you for sharing the log. Just to confirm, this is with the abortSignal workaround? Do you see my logs for "[connection-8]" afterwards?

@proohit Thank you very much for investigating and reporting the issue! React-Native is not officially supported yet by our SDK. We have https://github.com/Azure/azure-sdk-for-js/issues/5771 adding the support. Currently a couple packages...

> When the readme says to support browsers, what exactly is missing in react native? I don't know the exact gap until I try it first. I haven't tested our...

@proohit I just tried using "ws" in react-native. Unfortunately, react-native packager seemed to prefer the browser version and gave me [this error](https://github.com/websockets/ws/blob/master/browser.js#L4). I looked at `isomorphic-ws` but it looks just...

@proohit I found something during my investigation: react-native's `WebSocket.binaryType` by default is `undefined`, which is blocking rhea from behaving properly when running in browser. I will create an expo sample...

@proohit glad to hear that you got it running! Curious did you test on real hardware too, or just emulator? Yes, some nodejs modules are not really used when running...