You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Notes on transaction printing" in the docs state that "all print jobs submitted this time will loss if errors including out of paper, overheated occured, and an error feedback will be provided".
We use this to print bank receipts and get the result: proceed to next step after success or notify user in case of error. Basically, we submit the transaction and then wait for onPrintResult to be called.
This works well on Sunmi P2 Pro, but on Sunmi P1 4G this only handles errors happening during the printing. If there was already no paper when printing is started, onPrintResult is not called with an error code, and printer waits infinitely for paper to be inserted. And we don't see in the docs any methods to break this waiting manually (we tried calling enterPrinterBuffer(true) again, it didn't help).
We've tried versions 1.0.13 & 1.0.19, with the same result.
The text was updated successfully, but these errors were encountered:
"Notes on transaction printing" in the docs state that "all print jobs submitted this time will loss if errors including out of paper, overheated occured, and an error feedback will be provided".
We use this to print bank receipts and get the result: proceed to next step after success or notify user in case of error. Basically, we submit the transaction and then wait for
onPrintResult
to be called.This works well on Sunmi P2 Pro, but on Sunmi P1 4G this only handles errors happening during the printing. If there was already no paper when printing is started,
onPrintResult
is not called with an error code, and printer waits infinitely for paper to be inserted. And we don't see in the docs any methods to break this waiting manually (we tried callingenterPrinterBuffer(true)
again, it didn't help).We've tried versions 1.0.13 & 1.0.19, with the same result.
The text was updated successfully, but these errors were encountered: