We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Server Version: 2.8.4 Client Version: 1.11.2 - nats.ws (nats.js file is being used)
The client is running on android (tried both, the emulator and the actual device)
connect({ servers: server, //My Server URL i.e. wss://url.to.server/ws noEcho: true, token: sdjfhjsERDFDf, //A String is being used here }) .then((nc: NatsConnectionImpl) => { resolve(nc); }) .catch((reason) => { console.log("REASON>>>", reason); resolve(null); }) });
This should connect to the web socket and not give the timeout as it is running for the iOS version with the same code mentioned above.
For Android devices, I am getting connection timeout while it is working fine for iOS.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What version were you using?
Server Version: 2.8.4
Client Version: 1.11.2 - nats.ws (nats.js file is being used)
What environment was the server running in?
The client is running on android (tried both, the emulator and the actual device)
Is this defect reproducible?
connect({ servers: server, //My Server URL i.e. wss://url.to.server/ws noEcho: true, token: sdjfhjsERDFDf, //A String is being used here }) .then((nc: NatsConnectionImpl) => { resolve(nc); }) .catch((reason) => { console.log("REASON>>>", reason); resolve(null); }) });
Given the capability you are leveraging, describe your expectation?
This should connect to the web socket and not give the timeout as it is running for the iOS version with the same code mentioned above.
Given the expectation, what is the defect you are observing?
For Android devices, I am getting connection timeout while it is working fine for iOS.
The text was updated successfully, but these errors were encountered: