From b1afc26d650af33aa2700b7b2e6b7a32197b3a98 Mon Sep 17 00:00:00 2001 From: Adam Brown Date: Fri, 22 Oct 2021 12:09:13 +0100 Subject: [PATCH] using start_redeliver_intent to allow the system to restart killed sync services - memory restricted devices may have the sync service destroyed whilst in progress causing future sync to no longer be scheduled --- .../android/sdk/internal/session/sync/job/SyncService.kt | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/matrix-sdk-android/src/main/java/org/matrix/android/sdk/internal/session/sync/job/SyncService.kt b/matrix-sdk-android/src/main/java/org/matrix/android/sdk/internal/session/sync/job/SyncService.kt index 9480cc73f1..c17b31b910 100644 --- a/matrix-sdk-android/src/main/java/org/matrix/android/sdk/internal/session/sync/job/SyncService.kt +++ b/matrix-sdk-android/src/main/java/org/matrix/android/sdk/internal/session/sync/job/SyncService.kt @@ -105,9 +105,8 @@ abstract class SyncService : Service() { } } } - - // It's ok to be not sticky because we will explicitly start it again on the next alarm? - return START_NOT_STICKY + // Attempt to continue scheduling syncs after killed service is restarted + return START_REDELIVER_INTENT } override fun onDestroy() {