From 3f13fd78d0b8b7a12771c47ba47f19e8bf9073f3 Mon Sep 17 00:00:00 2001 From: Greyson Parrelli Date: Fri, 4 Sep 2026 14:16:26 -0400 Subject: [PATCH] Use writableDatabase in StorageAccountRestoreJob. --- .../thoughtcrime/securesms/jobs/StorageAccountRestoreJob.kt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/app/src/main/java/org/thoughtcrime/securesms/jobs/StorageAccountRestoreJob.kt b/app/src/main/java/org/thoughtcrime/securesms/jobs/StorageAccountRestoreJob.kt index f3e2dd713d..9727f80404 100644 --- a/app/src/main/java/org/thoughtcrime/securesms/jobs/StorageAccountRestoreJob.kt +++ b/app/src/main/java/org/thoughtcrime/securesms/jobs/StorageAccountRestoreJob.kt @@ -110,12 +110,12 @@ class StorageAccountRestoreJob private constructor(parameters: Parameters) : Bas val accountRecord = SignalAccountRecord(record.id, record.proto.account!!) Log.i(TAG, "Applying changes locally...") - SignalDatabase.rawDatabase.beginTransaction() + SignalDatabase.writableDatabase.beginTransaction() try { StorageSyncHelper.applyAccountStorageSyncUpdates(context, self().fresh(), accountRecord, false) - SignalDatabase.rawDatabase.setTransactionSuccessful() + SignalDatabase.writableDatabase.setTransactionSuccessful() } finally { - SignalDatabase.rawDatabase.endTransaction() + SignalDatabase.writableDatabase.endTransaction() } // We will try to reclaim the username here, as early as possible, but the registration flow also enqueues a username restore job,