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

NatsError: TIMEOUT for react native Android #221

Open
t2b-dev-mobile opened this issue Oct 30, 2023 · 3 comments
Open

NatsError: TIMEOUT for react native Android #221

t2b-dev-mobile opened this issue Oct 30, 2023 · 3 comments
Labels
defect Suspected defect such as a bug or regression

Comments

@t2b-dev-mobile
Copy link

What version were you using?

VERSION = '1.11.2';
LANG = 'nats.ws';

What environment was the server running in?

*Android Emulator: Pixel 3A
Actual Android Devices:
*Samsung Galaxy J5 Prime.
*Samsung A13

Is this defect reproducible?

"react-native": "0.70.8"

here is the code snippet that has been used to connect to the server.

connect({
    servers: wss://app.mydomain.com/ws
    noEcho: true,
    token: "Some String"
  })

Given the capability you are leveraging, describe your expectation?

Using the Above snippet and the client library version, I am able to connect to the server through iOS devices and iOS emulators but not able to connect using Android devices.

Given the expectation, what is the defect you are observing?

While trying to connect using Android, the following error has been faced:
"reader closed [TypeError: Object is not async iterable]" (This error has been consoled from the nats.js file)
[NatsError: TIMEOUT]: This is been consoled from the catch block of connect execution.

@t2b-dev-mobile t2b-dev-mobile added the defect Suspected defect such as a bug or regression label Oct 30, 2023
@aricart
Copy link
Member

aricart commented Nov 2, 2023

This issue is possibly for nats.ws, currently we don't support react native directly - I know of folks that have used it but not sure what the patching is to get it to work.

@aricart aricart transferred this issue from nats-io/nats.js Nov 2, 2023
@kindapath
Copy link

Please check this issue, you will probably find your solution

#195 (comment)

@t2b-dev-mobile
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defect Suspected defect such as a bug or regression
Projects
None yet
Development

No branches or pull requests

3 participants