What is the reason that the order not printed and only works after restart?
Which is more reliable to get the order printed?
Or there is a better solution to guarantee all orders printed?
Can you describe your use case for printing the order?
Can you post some sample code for how you are performing option 2: Send event to Android App (we found that sometimes the event not delivered)?
We have online order application. When user complete an order, we send printer command using two methods:
You can try on Clover API doc: https://www.clover.com/api_docs#!/not...
The payload we send to our app is { "event": "newonlineorder", "data": "OTHER NECESSARY ORDER INFORMATION"}
The problem is there was no complain before. But these past couple days there are many merchants complaining about order not printed or delayed.
Once it is received, it will call the Static ReceiptPrintJob SDK API.
Classname: com.clover.sdk.v1.printer.job
Below codes might be custom class we made based on Clover SDK
new StaticReceiptPrintJob.Builder().order(order).build() .print(PrintTestActivity.this, account);
Our notification service is not reliable. There's no guarantee when, or if you will receive the notification. If you need to guarantee that the message to print will be received by the device in a timely manner (which it sounds like is the case), you'll need to implement your own or use an existing reliable message delivery service.
@jeff do you mean for both notification to Android and fire order API are not reliable?
@yauri Both systems are using the same underlying notification system. So any reliability issues with one should be in the other. I would not recommend using the fire order API it is not documented or publicly supported
I would try to add a retry system to the Android notifications you are sending. This would probably require the app to respond back that it has received the notification you are sending.
@Voski ok I got it, we will add our retry system for the notification. Thanks! :D
3 People are following this question.
