Our foreground service is getting killed by operating system

Question

question

khurram asked Jul 10, '20 David Marginian Deactivated edited Jul 10, '20

Our foreground service is getting killed by operating system

Hi team,

we have a native application installed in our clover station which keep listening for our new online orders and when a new order comes it send a print job to print order.

We are using a foreground service to perform this listening process for new orders.

Now the problem is that after one or two days our foreground service get killed and after that our app won’t print any order and even we are not getting notified if our service is killed.

Please suggest us any solution to avoid our service being get killed?
or if we can avoid using foreground service and rely on some listeners of clover instead of this?

REST API Clover Station

10 |2000

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

Welcome to the
Clover Developer Community

Answer 1 · 2020-07-10T16:05:34Z

David Marginian Deactivated answered Jul 10, '20 David Marginian Deactivated edited Jul 10, '20

This is not a Clover specific problem, it is an Android problem, please see Jeffrey's response here: https://community.clover.com/questions/24078/how-to-set-listener-in-my-android-app-when-create.html.

There isn't a way to indefinitely listen for order updates because Android may remove your process because of memory / resource pressure from other apps. The best you can do is register your listener in a foreground service but even that is not guaranteed to keep it running.

The correct thing is to use Work Manager to periodically wake up and perform some work. This may not support your use case well however since Work Manager jobs aren't guaranteed to run at any particular time, and if you try to wake up frequently the OS is going to throttle your jobs.

2

10 |2000

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

khurram commented · Jul 10, 2020 at 04:16 PM

Actually clover rest api should have this printing feature for orders. This additional native app requirement is a lot of problem and we are really suffering with it.

0 ·

David Marginian ♦♦ khurram commented · Jul 10, 2020 at 04:59 PM

I understand the frustration, we do have some open issues for supporting this but it hasn't been a priority. There is a 3rd party app that I can't recommend (because I haven't tried using it) but you may want to investigate called Smart Print - https://www.clover.com/appmarket/apps/25BCJ2KGEJNEC.

0 ·

question