From d6426dc1b67a3030c6ed60e6bf74d875a4a13ca7 Mon Sep 17 00:00:00 2001
From: link2xt <link2xt@testrun.org>
Date: Sat, 1 Apr 2023 23:54:29 +0000
Subject: [PATCH] imex: run migrations after receiving a transferred backup

Similarly to how `imex_inner()` runs migrations
after successful call to `import_backup()`,
migrations should be run after receiving a backup
using `transfer_from_provider()`.
---
 CHANGELOG.md         | 6 ++++++
 src/imex/transfer.rs | 1 +
 2 files changed, 7 insertions(+)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 658c13925..76659da70 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,11 @@
 # Changelog
 
+## 1.112.5 - unrelesaed
+
+### Fixes
+
+- Run SQL database migrations after receiving a backup from the network. #4287
+
 ## [1.112.4] - 2023-03-31
 
 ### Fixes
diff --git a/src/imex/transfer.rs b/src/imex/transfer.rs
index 6156628a6..a9e7ff739 100644
--- a/src/imex/transfer.rs
+++ b/src/imex/transfer.rs
@@ -408,6 +408,7 @@ async fn get_backup_inner(context: &Context, qr: Qr) -> Result<()> {
     match transfer_from_provider(context, &ticket).await {
         Ok(()) => {
             delete_and_reset_all_device_msgs(context).await?;
+            context.sql.run_migrations(context).await?;
             context.emit_event(ReceiveProgress::Completed.into());
             Ok(())
         }