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
Hi @ekimcem, sorry for the delayed response. We do not develop on React Native so we didn't test it yet. Maybe you can experiment for yourself to see and let us know? :)
The results are acceptable. It worked on both iOS and Android native builds 👍 (with both Expo SDK 50 and 51).
The only thing we couldn't do with this package is programmatically close the WebSocket connection, because when we initialize this hook, it automatically connects to the WebSocket.
What we need is to trigger the connection programmatically. Maybe we couldn't find how to do this; I'm not sure.
The results are acceptable. It worked on both iOS and Android native builds 👍 (with both Expo SDK 50 and 51).
The only thing we couldn't do with this package is programmatically close the WebSocket connection, because when we initialize this hook, it automatically connects to the WebSocket.
What we need is to trigger the connection programmatically. Maybe we couldn't find how to do this; I'm not sure.
Thats cool to hear! How does this hook even work with your web socket connections? Since we made this hook to only fire HTTP calls to a specific endpoint.
Description:
I'm exploring the compatibility of your React hook for streaming responses with React Native Expo SDK 50.
Details:
Compatibility Inquiry: Is the streaming hook compatible with React Native Expo SDK 50?
Environment Information:
React Native Expo SDK version: 50
Thank you for your guidance on this matter!
The text was updated successfully, but these errors were encountered: