You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By calling ContextCompat.startForegroundService continuously to interact with TracingService and returning always START_REDELIVER_INTENT in its onStartCommand, if the OS (or you yourself) kills the service, when restarted it re-executes absolutely every intent that was executed in the past, all in a raw (the ACTION_START, all the numerous ACTION_RESTART_SERVER and all the even more numerous ACTION_RESTART_CLIENT). That is absolutely unnecessary and slows down the app and the system.
Not sure if the solution is to return START_REDELIVER_INTENT only on ACTION_START, return always START_NOT_STICKY or re-thinking the service...
The text was updated successfully, but these errors were encountered:
simonroesch
added
the
prestandard
This issue is referring to the "prestandard" solution and not the current GAEN implementation.
label
May 19, 2020
Hi,
By calling
ContextCompat.startForegroundService
continuously to interact withTracingService
and returning alwaysSTART_REDELIVER_INTENT
in itsonStartCommand
, if the OS (or you yourself) kills the service, when restarted it re-executes absolutely every intent that was executed in the past, all in a raw (theACTION_START
, all the numerousACTION_RESTART_SERVER
and all the even more numerousACTION_RESTART_CLIENT
). That is absolutely unnecessary and slows down the app and the system.Not sure if the solution is to return
START_REDELIVER_INTENT
only onACTION_START
, return alwaysSTART_NOT_STICKY
or re-thinking the service...The text was updated successfully, but these errors were encountered: