Closed franz-ms-muc closed 2 years ago
This exception comes from:
Which might "theoretically" happen only if the command AT+CGNSINF
were issued second time after failing on timeout for the first time. Not sure if it was, however, if this was your original code:
Anyway, there seems to be a bug, revealing the timeout race condition (should the response come just after the operation timeouted). The quick fix is to add
signal.clear(GOT_LINE);
just after
it seems there is an exception somwhere,
i assume from "throw" ...