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

Invalid argument(s): length must be in the range [0, 4611..] #71

Open
MervePlt opened this issue Apr 4, 2023 · 8 comments
Open

Invalid argument(s): length must be in the range [0, 4611..] #71

MervePlt opened this issue Apr 4, 2023 · 8 comments
Labels
help wanted Extra attention is needed investigation

Comments

@MervePlt
Copy link

MervePlt commented Apr 4, 2023

It does not show this error all the time, but when it does, the communication can not be established by this port again. But, turning it off and on manually fixes the problem. However, we can not count that as a constant solution for this problem. Is there any other way we can follow to solve it automatically? (without turn the port on and off MANUALLY)

hata_4_4_2023_

@joaquin-amenta
Copy link

Same here, have you found a solution?

@mingpepe
Copy link

sp_nonblocking_read may return negtive value on error. This library assume that read operation is always success. If the return value is negative, asTypedList may throw that exception.

You can use sp_last_error_message to check what error occured.

@Ido-Sobol
Copy link

sp_nonblocking_read may return negtive value on error. This library assume that read operation is always success. If the return value is negative, asTypedList may throw that exception.

You can use sp_last_error_message to check what error occured.

How do I call sp_last_error_message when I'm using flutter_libserialport and not libserialport?

@mingpepe
Copy link

mingpepe commented Jun 12, 2023

@lucafabbri
Copy link
Collaborator

Could anyone check this one as 0.4.0 is available on pub.dev?

@lucafabbri lucafabbri added help wanted Extra attention is needed investigation labels Feb 21, 2024
@samuelishimwe
Copy link

@lucafabbri Am currently on 0.4.0 but am facing the same issue

@MironRobert
Copy link

Has anyone found something about this issue? I have the same issue but not at the same place. Because for me, it happens only when I manually turn it OFF and ON.

The only thing I know is that, just disconnecting the port gets an "errno = 5" (and can sometimes crash the app). Yet reconnection automatically gets "errno = 0".

But to get that i just printed ("SerialPort.lastError") and the Unhandled exception wasn't there anymore. Just the errors listed before.

And i just don't understand why at some point the errno = 5 crashes my app.

I'm in 0.4.0.

@jsalvini
Copy link

I am also on version 0.4.0 and facing the same problem, any solution to this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed investigation
Projects
None yet
Development

No branches or pull requests

8 participants