Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility Inquiry: React Native Expo SDK 50 Support #35

Open
ekimcem opened this issue Apr 20, 2024 · 3 comments
Open

Compatibility Inquiry: React Native Expo SDK 50 Support #35

ekimcem opened this issue Apr 20, 2024 · 3 comments

Comments

@ekimcem
Copy link

ekimcem commented Apr 20, 2024

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!

@niels-bosman
Copy link
Member

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? :)

@ekimcem
Copy link
Author

ekimcem commented May 24, 2024

Hi again!

After creating this, I have tested it. :)

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.

@niels-bosman
Copy link
Member

Hi again!

After creating this, I have tested it. :)

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants