From 892771288150c0c64acbd256a2bfd9f40ef19ecf Mon Sep 17 00:00:00 2001 From: Kyle Van Essen Date: Wed, 5 Aug 2026 21:10:14 -0700 Subject: [PATCH 1/2] Fix backup share sheet presentation --- .../Sources/Settings/BackupArchiveFile.swift | 24 ------------------- .../Settings/BackupSettingsSection.swift | 4 ++-- 2 files changed, 2 insertions(+), 26 deletions(-) delete mode 100644 Where/WhereUI/Sources/Settings/BackupArchiveFile.swift diff --git a/Where/WhereUI/Sources/Settings/BackupArchiveFile.swift b/Where/WhereUI/Sources/Settings/BackupArchiveFile.swift deleted file mode 100644 index de8dba5b..00000000 --- a/Where/WhereUI/Sources/Settings/BackupArchiveFile.swift +++ /dev/null @@ -1,24 +0,0 @@ -import CoreTransferable -import UniformTypeIdentifiers - -/// A ready-on-disk backup archive shared through `ShareLink`. The export is -/// built up-front (see `BackupModel.exportBackup`), so this just wraps the -/// finished file — but wrapping it in an explicit `.zip` `FileRepresentation`, -/// rather than sharing a bare `URL`, keeps the exported content type declared -/// instead of inferred from the filename extension. -/// -/// `suggestedFileName` is load-bearing: sharing a custom `Transferable` (rather -/// than a bare `URL`) means many share targets ignore the file's on-disk name -/// and synthesize one from the `SharePreview` title. Forwarding the archive's -/// real name (`Where Backup