"Printing Sales Receipt" Spinning Error

[CentralBooks]

In the past 48 hours, my handheld square has starting doing this thing where, after it prints the receipt, it shows a spinning circle and the message "Printing Sales Receipt" (even thought the receipt just printed.) And it keeps spinning for about 45 seconds to minute until it goes away and we can check out the next customer. Which is a pain when it's busy!

I confirmed with my neighboring store that she is also having the same problem. So, it's a Square problem, not a me problem.

[mitin]

Hi @CentralBooks 
Try these steps, I hope it helps

Even if it's a Square-wide issue, a soft reset can sometimes force the device to drop a "stuck" background process:

• Hold the power button for about 15–20 seconds.

• Do not release it when the "Restart" option appears; keep holding until the screen goes black and the device fully shuts down.

• Turn it back on. This clears the local print queue and can sometimes refresh the connection to Square's servers.

2. Toggle "Automatically Print Receipts"

If the spinning happens after the paper has already come out, the "confirmation" signal is getting looped. You can try disabling the automatic trigger to see if manual printing is faster:

• Go to ≡ More > Settings > Hardware > Printers.

• Select the Built-in Printer.

• Toggle Automatically Print Receipts to OFF.

• Test: After the next sale, manually tap "Print Receipt." If it prints and finishes immediately, the "Automatic" handshake was the culprit.

 

[tesselaar]

thanks for the response @mitin MITIN .

Im having the same problem today (it didnt occur yesterday!). 

Ive tried the following without success

* regular "restart".

* hold power button for 15-20 seconds to reboot

* Turning Automatically Print Receipts to OFF and manually printing receipt.

Other observations

Reprinting a receipt from the "Transactions" page doesnt cause a problem.

The same issue occurs on cash payments.

[offgridcafe]

having same issue any advice or resolution?

[offgridcafe]

appears to have resolved itself?  maybe was a server side issue