question

brandin avatar image
brandin asked David Marginian Deactivated commented

Testing App Notification on Production

We've created a Clover application that when it receives a push notification via 

v3/apps/x/devices/y/notifications

it triggers a print job for a Clover order ID it receives as part of the POST body to the above endpoint.


Now for the issue -- this works in the sandbox environment, but does not seem to work in the production environment. We've triple checked the endpoints, the IDs, and the Authorization. The API returns a successful 2xx response code, but no print is triggered.


Compounding the issue is that we are relying on the merchant to tell us whether or not the process works, since the production deployments are all remote.


My question is what is the recommended process for debugging Clover notifications on a production device?

REST API
10 |2000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

1 Answer

David Marginian avatar image
David Marginian Deactivated answered David Marginian Deactivated commented

You can add some logging in your app that writes out critical events to a server you have access to. Otherwise there aren't a ton of options. You can have the merchant send us the device logs via the help app (help - menu - diagnostics - send device logs). This would need to be done right after an order didn't print (device logs are cleared nightly).

7 comments
10 |2000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

brandin avatar image brandin commented ·

Are there any obvious things that you could think of for us to look at to determine why this works in the sandbox but not in production?

We'll add the remote logging and see what that shows us, but the constant back and forth of adding logging, re-releasing the app, testing, adding more logs/fixing things, re-releasing is a huge pain considering the approval time seems to be fairly long for production atm.


0 Likes 0 ·
David Marginian avatar image David Marginian ♦♦ brandin commented ·

Have you tested with the device type that is being used in prod?

If you want to create a private post (viewable by moderators and original poster) and include the device serial number (or uuid) this is happening on and the ~ times I can look at the current logs and or check for crashes. You may want to fire a print and then have the merchant send the logs via the help app (help -> menu -> diagnostics -> send device logs). This needs to be done shortly after the print is fired.

0 Likes 0 ·
brandin avatar image brandin David Marginian ♦♦ commented ·

The app is being tested on our Sandbox Clover Station, and one of the client's production Clover Stations.

They're using the newest model station, while we are using a much older one.


How would I coordinate with someone from Clover to review the logs? Does it need to be done in real-time? Does the submit logs action from the Clover terminal clear after a certain period of time, or is it always there to review?

0 Likes 0 ·
Show more comments

Welcome to the
Clover Developer Community