question

ismdcf avatar image
ismdcf asked ·

"StaticReceiptPrintJob - Print" Notifies with printing error.

We are using the following code to print orders receipts on our android application,
by using the following code

new StaticReceiptPrintJob.Builder().order(mOrder).build().print(currentActivity, account, printer);
Printing was working as expected in the Devkit, recently we are facing an issue, where the printer does not print but it shows an error notification and we get the following error on the logcat
W/SeikoMini: onHandleIntent(PrinterIntentService.java:404): print failed, printer: Printer{uuid=6KMYS7D92MK48, type=SEIKO_MINI_USB, name=Mini, mac=null, ip=null, category=RECEIPT}
                                             java.lang.NullPointerException
                                                 at com.clover.engine.services.ReceiptPrinterPlugins.ReceiptGenerator.createReceiptView(ReceiptGenerator.java:256)
                                                 at com.clover.engine.services.ReceiptPrinterPlugins.ReceiptGenerator.createReceiptView(ReceiptGenerator.java:227)
                                                 at com.clover.engine.services.ReceiptPrinterPlugins.seiko.SeikoMini.printReceipt(SeikoMini.java:76)
                                                 at com.clover.engine.services.PrinterIntentService.onHandleIntent(PrinterIntentService.java:323)
                                                 at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)
                                                 at android.os.Handler.dispatchMessage(Handler.java:102)
                                                 at android.os.Looper.loop(Looper.java:136)
                                                 at android.os.HandlerThread.run(HandlerThread.java:61)
What could be the reason for this null pointer exception, We have also tried to update to the latest version of clover android sdk (191.3) but the error is still not fixed.
OrdersPrintDevKit
10 |2000 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

chanel avatar image
chanel answered ·
We're aware of this error and are in the process of fixing this. In the meantime, I suggest that you use other print jobs like StaticOrderPrintJob or StaticBillPrintJob.

I'll keep you updated for when we've rolled out the fix.

(2/27 - Edit) It looks like the rollout was successful and the printing error should no longer occur on Production. If anyone is continue to see any issues with this, please let me know!
6 comments Share
10 |2000 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Thank for the reply,

Our requirement is to use StaticReceiptPrintJob, So is there any update on fixing this issue.

Also, could you clarify if this error is occurring only on sandbox provisioned devkits or on Production devices as well.

Regards

0 Likes 0 · ·

If you don't mind my asking, why is the requirement to use StaticReceiptJob?

This error appears in Production and Sandbox and the fix is currently being verfied and tested internally.

0 Likes 0 · ·

Once again thanks for the reply,

We checked our sandbox provisioned devkit, it still gave us the same error. is it possible to verify if the update was installed on our devkit (like a version number check of the clover printer plugin ...). Or is this fix applied only on production devices.

Regards

0 Likes 0 · ·

Yep the issue is fixed as of 3/3/2018 on the sandbox environment.

0 Likes 0 · ·

Hi @Chanel , Just wanted to verify if this fix was applied to production. If so is there a way for our clients to verify whether they have the bug free versions updated (like a version check for the printer app or so).

And also is it possible that a particular merchant might have disable automatic updates and therefore have not recieved this update, is that possible?

0 Likes 0 · ·

Hi @ismdcf, This should have been applied to our US production servers on Feb 27th. At this point, all US Clover devices that are connected to the internet should have this version. Due to PCI compliance, the devices restart every night to allow for such updates to occur.

Please have them check the current version of the software (Settings > Storage > Apps > Clover; here you should see a version greater than 1923 (the version with the fix))

Please let me know if this is not the case.

0 Likes 0 · ·

Welcome to the
Clover Developer Community