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

HandshakeException #119

Open
marcodecarolisidt opened this issue Nov 24, 2022 · 8 comments
Open

HandshakeException #119

marcodecarolisidt opened this issue Nov 24, 2022 · 8 comments
Assignees
Labels
bug Something isn't working wontfix This will not be worked on

Comments

@marcodecarolisidt
Copy link

marcodecarolisidt commented Nov 24, 2022

Describe the bug
We keep having random exceptions:

[ERROR] 15:27:26 Failed to fetch calling rates, msg: HandshakeException: Handshake error in client (OS Error:
	WRONG_VERSION_NUMBER(tls_record.cc:242))

And it is impossible to know how to fix it

Please complete the following information):

  • Flutter version: 3.3.6
  • IDE [VS Code]
  • http_interceptor Version [1.0.2]
@marcodecarolisidt marcodecarolisidt added the bug Something isn't working label Nov 24, 2022
@CodingAleCR
Copy link
Owner

Taking a look 👀 , could you provide a repository that reproduces this issue?

@marcodecarolisidt
Copy link
Author

marcodecarolisidt commented Nov 29, 2022

Sorry, I can't it's a private repo..
So we fire some asynchronous API requests when the app starts. And sometimes, some of them fail randomly, and the fetch doesn’t work. I tried to override shouldAttemptRetryOnException to return true, but it doesn't solve the issue

@marcodecarolisidt
Copy link
Author

Will a package upgrade to the beta version fix the issue? if yes when will the beta version become stable? thank you 🙏

@CodingAleCR
Copy link
Owner

Sorry, I can't it's a private repo.. So we fire some asynchronous API requests when the app starts. And sometimes, some of them fail randomly, and the fetch doesn’t work. I tried to override shouldAttemptRetryOnException to return true, but it doesn't solve the issue

It doesn't have to be the exact repository you are working but maybe an example that reproduces the issues?

Will a package upgrade to the beta version fix the issue? if yes when will the beta version become stable? thank you 🙏

I believe that it won't do any difference to change to the beta version. 2.0.0 is a complete rewrite of the library to support multiple request types and scenarios but it also takes a couple of ideas from 1.x so I think you won't see any differences. You could try to see if that solves the issue but as to when this will become stable I can't give you an answer. My day job requires a lot of me so I can't dedicate as much time to Open Source as I'd like. :[

@stale
Copy link

stale bot commented Mar 18, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Mar 18, 2023
@stale stale bot closed this as completed Apr 2, 2023
@CodingAleCR CodingAleCR reopened this May 4, 2023
@stale stale bot removed the wontfix This will not be worked on label May 4, 2023
@Aakashcs
Copy link

Aakashcs commented May 5, 2023

Any update on this issue @CodingAleCR?

@CodingAleCR
Copy link
Owner

Not from the library, but just curious, have any tried the solutions proposed in this stackoverflow thread.

@stale
Copy link

stale bot commented Sep 17, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Sep 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants