From 3d7a4146e41aba95de36e23950301c11ae128b9e Mon Sep 17 00:00:00 2001
From: schroda <50052685+schroda@users.noreply.github.com>
Date: Mon, 6 Jan 2025 01:58:49 +0100
Subject: [PATCH] Handle metadata key deletion early exit

In case no keys had to be deleted it always returned an empty object which broke the whole metadata migration and resulted in the final metadata to always fall back to the default values
---
 src/modules/metadata/services/MetadataMigrations.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/modules/metadata/services/MetadataMigrations.ts b/src/modules/metadata/services/MetadataMigrations.ts
index d0a1d14a..754e8cff 100644
--- a/src/modules/metadata/services/MetadataMigrations.ts
+++ b/src/modules/metadata/services/MetadataMigrations.ts
@@ -140,7 +140,7 @@ const applyMetadataDeleteKeysMigration = (
     const migratedMetadata: Metadata = {};
 
     if (!migration.deleteKeys) {
-        return migratedMetadata;
+        return { ...meta };
     }
 
     const appMetadata = getAppMetadataFrom(meta, undefined, appKeyPrefix);