You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The properties url, protocol, and bufferedAmount on instances of WebSocket are returning undefined (on iOS at least).
I'm able to successfully connect using both of the given values, but accessing either doesn't work as expected. This causes problems for clients that depend on having either value.
However, readyState seems to be working correctly. I haven't checked extensions.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.
stalebot
added
the
Stale
There has been a lack of activity on this issue and it may be closed soon.
label
Sep 12, 2019
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.
The properties
url
,protocol
, andbufferedAmount
on instances ofWebSocket
are returning undefined (on iOS at least).I'm able to successfully connect using both of the given values, but accessing either doesn't work as expected. This causes problems for clients that depend on having either value.
However,
readyState
seems to be working correctly. I haven't checkedextensions
.React Native version:
Steps To Reproduce
WebSocket
that uses a subprotocolurl
orprotocol
Describe what you expected to happen:
If I do
const ws = new WebSocket('ws://localhost:8080
, 'some-protocol')`ws.url
andws.protocol
should returnws://localhost:8080
andsome-protocol
respectively.Snack, code example, or link to a repository:
https://github.com/NRauh/react-native-websocket-issue
Here's a minimal example of a ws server and clients. The browser client works as expected, but the react native app does not.
The text was updated successfully, but these errors were encountered: