[Tracker] AeroFTP 4.1.5 - Known issues, patches & updates

[axpnet]

AeroFTP 4.1.5, Rolling Tracker

Umbrella issue for the next AeroFTP point release (v4.1.5): known issues reported against v4.1.4 and the patches/updates landing on main after the v4.1.4 tag.

Status note: the current release line is v4.1.4 (release notes, its tracker is #1412, now closed); this tracker collects what lands on main for v4.1.5.

Before opening a new issue, please check the lists below. If your problem is already tracked here, just add a thumbs-up reaction or a comment with your environment (OS, version, provider) instead of filing a duplicate. We update this issue as bugs are found and fixed.

Found something that is not listed? Open a new issue and we will link it here.

What shipped in 4.1.4

See the v4.1.4 tracker (#408) and the release notes for the full 4.1.4 change set: archive encryption, compression method and AeroVault generation surfaced at a glance in both the local and the remote file browser (padlock, real detected cipher, Encryption/Compression columns and AeroVault chip, header-only and download-free), an optional keyfile second factor for native AeroCrypt (a "something you have" file mixed into the KDF, keyfile-only vaults allowed, travelling fail-closed through profile export/import), the AeroCrypt default flipped to a lean headerless base with the recovery kit now optional, on-demand and working in every mode (headerless, headed, keyfile), the crypt overlay scope completed with a dedicated Overlays Remote Path sub-scope input and CLI crypt bind (plaintext outside the bound subtree, decrypt only inside, across GUI, CLI and MCP), safer destructive CLI deletes and MCP recursion now opt-in and fail-closed, full S3 trash and version management from the GUI, CLI and MCP with a live-file safety fix, roughly 3x faster recursive SFTP listing, macOS promoted to stable and now shipping signed, a CLI --machine agent-output mode with a remote find-and-replace edit command and MCP aeroftp_edit tool, a broad AeroCloud expansion (multiple sync pairs, delete propagation, send-only/receive-only folders, CLI reachability, SFTP key auth, tunable watcher and a compress overlay), the drift-proof aeroftp-cli inventory command-and-tool SSOT, an app-wide Date format setting, the Windows archive opener registration and an in-app File associations settings panel, and a security audit the length of the cycle (AeroFile B1 17/17, integer-overflow guards on the remote archive-detect path, no walker follows a symlink-to-directory cycle, per-scope keyring isolation so a sandbox cannot lock a native vault, a signed macOS dmg, and a full pre-release plus pre-tag commit audit, both PASS). 47 languages translated.

Patches & updates queued for 4.1.5

Landed on main after the v4.1.4 tag; shipping in v4.1.5.

#	Type	Change	Status	Commit	Ref
1		Emergency Kit recovery wording no longer contradicts itself. The printed kit and the recovery-kit panel copy told the user both to save the kit "together with your password" and to "NEVER store the password alongside this kit". Reworded to separate the functional requirement (the kit and the password are both required to recover a vault, neither one alone can open it) from the security rule (keep them in separate places). Retranslated recoveryKitIntro across all 46 non-EN locales, keeping the mode-agnostic wording	🟢 done	39455a150	#276 (@EhudKirsh)
2		Non-identical duplicate detection is complete across the engine, GUI, CLI and agent tools. The shared engine routes raster files through pHash, text including .svg through SimHash with a MinHash cross-check, and Other byte payloads through pure-Rust TLSH (tlsh2). The CLI and GUI expose Exact / Non-identical modes, local_find_duplicates now delegates to the shared engine and returns similarity metadata, and aeroftp_dedupe / remote_dedupe support non-identical staging with similarity and distance while preserving the remote exact SHA-256 fast path. Non-identical mode remains opt-in and never auto-selects files for deletion	🟢 done	271d78448, d3c732269, f5199c909, 300de974, c475fb86	#383 (@EhudKirsh)
3		AeroCrypt default-salt portability and TSV marker migration are complete. Default-salt mode is an advanced opt-in with password-strength gate, explicit attestation, and salt-mode MAC binding; the recovery kit has QR export controls; new headed markers write .aerocrypt.tsv while legacy .aeroftp-crypt.json remains readable, and CLI/GUI migration verifies the new marker before deleting the old one. The Linux release workflow also retries transient Tauri AppImage helper downloads	🟢 done	c7ff673a, 78daa525, fe0a9914, 4b0b6c8e, 9f5745da	#276 (@EhudKirsh)
4		Password Forge and encrypted-provider credential hardening are complete. Security Tools is always discoverable; the generator now supports reusable presets including Compatible 32, granular and custom character sets, exclusions, guaranteed selected groups, batch generation and live entropy; inline generation covers AeroVault, encrypted overlays and protected archives. Saved Filen/MEGA 2FA secrets are demoted behind a collapsed advanced disclosure with an honest warning, Filen bridge credentials enforce the documented 32-character restrictions, MD5/SHA-1 are marked legacy, and the provider guide documents credential scope and least-privilege bridge options	🟢 done	eccf8f4b	#266, #369 (@EhudKirsh)
5		Emergency Kit validity check is complete (crypt kit-verify + GUI Verify). A saved kit text, QR dump, .aerocrypt.tsv or legacy .aeroftp-crypt.json can be re-parsed offline and checked against the active profile keystore (vault ID, salt, version, KDF) without a recovery drill or password. CLI crypt kit-verify --profile … --kit …, Tauri aerocrypt_verify_recovery_kit, Recovery Kit modal Verify action with native Save/Print, profile-slug default filenames, and clearer kit notices (info vs legacy upgrade). New headed vaults still write TSV; legacy JSON stays readable	🟢 done	3e78f1e8	#276 (@EhudKirsh)
6		Missing headed marker is rebuilt from the local keystore with a one-shot lockout warning. When a headed vault's remote marker is gone, unlock no longer silently degrades to headerless: the marker is restored from the keystore and the user is told not to delete it again. Profile withHeader is plumbed end-to-end; legacy JSON to TSV conversion is opt-in from the AEROCRYPT badge menu (Convert marker, only when JSON is still present). Marker ops peel to the raw transport under an active overlay; pre-Tier-1 configs get a vault_id keystore backfill for kit readiness	🟢 done	3e78f1e8	#276 (@EhudKirsh)
7		CLI machine mode and banner suppression now honor environment variables consistently. AEROFTP_MACHINE (truthy) enables machine/agent output mode as an equivalent to --machine, resolved right after argument parsing so agents and CI no longer repeat the flag on every call, and AEROFTP_NO_BANNER is realigned to the same strict_env_truthy convention as AEROFTP_STRICT and AEROFTP_MACHINE (only 1/true/yes/on suppress; =0 and =false no longer do)	🟢 done	1bbe7d59, e98dbcbc	-
8		Classic-rsync transfers now animate a live progress bar instead of jumping at the end. The classic rsync path (system rsync binary, --info=progress2) parsed live progress lines but dropped them, so a delta transfer over that path showed no movement until the final summary. The existing progress sink is now threaded through RsyncBinaryTransport into run_rsync and called on each parsed progress line, deriving the total from the cumulative bytes and percent, matching the native delta path. The stdout loop was extracted into a tested helper	🟢 done	98632670	-
9		A drive inserted while AeroFTP is in the background now appears in the PLACES sidebar as soon as the window regains focus. On Windows and macOS the volume watcher falls back to a 30s poll (real-time inotify is Linux-only), so a freshly attached drive could take up to 30s to show. AeroFile now refetches mounted volumes and unmounted partitions on window focus. This is the lighter mitigation of the #351 hotplug idea; Linux is unaffected (the watcher already updates instantly)	🟢 done	4da7a3dd	#351 (@EhudKirsh)
10		Release hygiene: green CI and complete translations. Applied cargo fmt to the aerocrypt kit-verify hunks that commit 3e78f1e8 left unformatted (the Checks cargo fmt --check gate was red on main), and translated the aerocryptNative.legacyMarkerConvertAction ("Convert marker") label into all 46 non-EN locales so i18n:validate reports zero placeholders	🟢 done	d32a76a8, a8cafd12	-
11		The transfer queue now survives an app restart (backend journal). Interrupted queue items are persisted atomically to aeroftp_data_root/transfer-queue/queue.json as re-executable descriptors (direction, local and remote path, profile id, size, status, attempts), with load and clear helpers and an interrupted-entries query for restart detection, plus three Tauri commands. This is TQ-7a: persistence and detection only; the frontend restore that re-queues interrupted items on startup is TQ-7b, and per-provider byte-range resume stays deferred (TQ-7c)	🟢 done	f5f1b9be	-
12		Interrupted transfers are restored on the next launch. The frontend now persists the queue as it changes and, on startup, brings back any transfer that was still pending or in flight as a re-queueable "Restored" item (badge plus Retry), joining a side map of per-item local, remote, and profile descriptors and mapping the UI statuses to the journal. Restored items do not auto-start or auto-reconnect: after reconnecting to the same server, Retry re-runs them through the normal transfer path (uploads use an explicit remote directory taken from the journal). Verified live end to end (persist, restart, restore, real re-upload of a 100 MB file). This is TQ-7b; per-provider byte-range resume stays deferred (TQ-7c)	🟢 done	42935d65	-

Requested / under consideration

Community requests and internal follow-ups being evaluated for this or a later release.

Effort: 🟩 quick win · 🟧 medium · 🟥 large / epic. Ordered by effort (quick wins first).

#	Effort	Type	Request	Status	Source
1	🟧		Windows hotplug detection in the AeroFile PLACES sidebar is slow: a freshly inserted drive can take up to ~30s to appear, because the real-time volume watcher is Linux-only (inotify) and Windows/macOS fall back to a 30s poll. A Rust-side WM_DEVICECHANGE listener emitting volumes-changed on device arrival/removal would make it instant; lighter mitigations are a refetch on window focus or a shorter poll interval. Surfaced during the #351 eject verification on real Windows hardware	🔵 idea	#351 (@EhudKirsh)
2	🟧		Eager-evaluation preview and a single-vs-multi-target placeholder for the -i selectors (prioritised by the reporter ahead of Edit(E) and the 2-letter semantics; exact behaviour to be pinned)	🔵 idea	#311 (@EhudKirsh)
3	🟧		AeroSync Compare crypt-awareness: the crypt-overlay epic shipped a name-aware Compare in v4.1.4 (both rclone-crypt and AeroCrypt decrypt remote names at compare time, so a scheduled or incremental sync no longer re-uploads the whole folder each run), and rclone-crypt is size-aware too. The only residual is AeroCrypt content-size decryption at compare time (needs the versioned overlay container decoder), deliberately deferred: until it lands a size-policy compare may still re-flag AeroCrypt files. Tracked as finding I1 in the crypt-overlay epic	🔵 planned	#347 (@EhudKirsh)
4	🟥		MTP / portable-device provider for AeroFile: surface attached MTP/WPD devices that have no drive letter (phones, cameras; the reporter's Sony Xperia is one) in PLACES, browse the object tree as a virtual path, and copy whole files to and from the device. A design appendix is written (design only, no implementation): it documents the protocol and its hard MTP/OS limits (no real mount, no random access, no delta or resume, whole-file transfers only, best-effort metadata) so they are never read as an AeroFTP shortcoming, and maps the capability onto the existing StorageProvider trait, recommending a hybrid model. Implementation is a later, separate effort	🔵 idea	#351 (@EhudKirsh)
5	🟥		Lossless .jpg to .jxl transcode in AeroFile: JXL re-encodes an existing JPEG losslessly and reversibly (the original JPEG bytes reconstruct exactly), for a real size win with no quality loss. Candidate framing: AeroFile as a GUI for libjxl	🔵 idea	aerovault#2 (@EhudKirsh)
6	🟥		macOS shell integration for the OS extract feature (Deliverable G macOS, deferred): Finder Sync "Extract Here / Extract to Folder" menu items mirroring the Linux Nautilus and Windows verbs, plus macOS custom document-type icons (CFBundleDocumentTypes) for the five aero formats and the generic fallback, and rebuilding the mimetype .icns multi-size (the v4.1.0 ones are single-resolution drafts). Needs a Mac to build and live-test	🔵 planned	#1408 (Deliverable G)
7	🟥		Filen Encrypted Notes: exit Beta: take Filen Notes out of Beta. Fix the participants/add contactUUID format (currently a best-effort workaround), investigate the Filen free-plan 10-note limit ghost-note cleanup, and add a rich text editor for the rich note type	🔵 planned	-
8	🟥		PRIORITY: Linux tray/GTK heap corruption, still-uncovered off-main-thread corruptor. A GDBus worker thread aborts with malloc(): unaligned fastbin chunk detected while deserializing a D-Bus message, the classic GLib heap-corruption signature (that worker is the victim tripping over an already-poisoned fastbin, not the corruptor). Two marshalling fixes already shipped and are safe: tray badge (31db84f8b) and app_ready + splash-timeout (cae95ee91), present since v4.0.5. But the SIGABRT STILL recurs (v4.0.9 on 2026-06-25, and the v4.1.2-era build on 2026-07-05, identical signature): the marshalling is INCOMPLETE, a still-uncovered off-main-thread GTK path remains. Sync Tauri commands are provably main-thread (safe), so the suspects are the event/plugin callbacks whose thread context is unconfirmed: tray on_menu_event / on_tray_icon_event, the single-instance plugin callback, and on_window_event CloseRequested. Pre-existing across versions, intermittent, triggered by D-Bus storms on suspend/resume or monitor standby; it can corrupt the whole app until restart. Definitive path (owner-approved): adopt self-hosted crash reporting with native minidumps to capture the real corruptor, plus an ASan/valgrind repro, then finish the marshalling on the remaining callbacks	🔵 planned	-
9	🟥		User-supplied custom CSS snippets (Obsidian snippets-folder style) to restyle app chrome such as the preview scrollbar, applied across desktop and future mobile. Noted when the preview scrollbar was widened in v4.1.1	🔵 idea	#347 (@EhudKirsh)
10	🟧		Startup "resume queue" prompt for restored transfers. TQ-7b restores interrupted transfers silently as pending "Restored" items with a per-item Retry, but that Retry is easy to miss (surfaced in live testing). A startup banner or prompt ("N interrupted transfers from a previous session: Resume all / Discard") would make the resume action discoverable, matching the existing AeroSync resume-banner pattern	🔵 idea	-

Known issues found after release

Reported against v4.1.4. Fixed items ship in v4.1.5; reporters close after confirming in the release.

#	Area	Description	Status	Linked issue

_{Status legend: 🔴 confirmed · 🟡 investigating · 🔵 planned / idea · 🟢 done / fixed (pending release) · ✅ released}

Affected platforms

• Windows
• macOS
• Linux

---

Maintained by the AeroFTP team. Current release v4.1.4 (#408), next v4.1.5. Patches accumulated here; each release line still gets its own tracker.

[axpnet]

Emergency Kit recovery wording no longer contradicts itself

Post-4.1.4 follow-up, fixed on main, shipping in v4.1.5 (#276, reported by @EhudKirsh).

The Emergency Kit copy told the user two things that cannot both hold: one line said to save the kit "together with your password", another said to "NEVER store the password alongside this kit". The intent was the functional fact (you need the kit AND the password together to recover), not the physical instruction (keep them in the same place). The wording collapsed those into a self-contradiction. Reworded so the two ideas are separate and consistent.

Area	Description	Status	Ref
Printed kit text	render_text now reads "Keep this in a safe place. You will need it TOGETHER WITH your password to recover your vault" and "SECURITY: NEVER keep this kit and your password in the same place. Both are required to open the vault; neither one alone can"	🟢 fixed	39455a150
Panel copy	aerocryptNative.recoveryKitIntro reworded: both required, kept in separate places, neither one alone can open the vault	🟢 fixed	39455a150
Localization	recoveryKitIntro retranslated across all 46 non-EN locales in the same commit, mode-agnostic wording preserved	🟢 fixed	39455a150

Verified green: cargo test aerocrypt::emergency_kit (4 passed), cargo fmt --check clean, npm run i18n:validate 47 locales (0 missing, 0 extra, 0 NEEDS TRANSLATION).

[axpnet]

Non-identical duplicate detection complete across engine, CLI, GUI and agent tools

Post-4.1.4 follow-up, shipped on main, shipping in v4.1.5 (#383, requested by @EhudKirsh).

AeroFile already finds byte-identical duplicates. The v4.1.5 line now also finds duplicates that are similar but not byte-identical, with the similarity function chosen per file type rather than one hash for everything. Exact mode is untouched, non-identical mode is opt-in, and non-identical groups never auto-select files for deletion.

Area	Description	Status	Ref
Shared engine	src-tauri/src/dedupe/ routes raster files through perceptual pHash, text including .svg through SimHash plus a MinHash cross-check, and Other byte payloads through TLSH (tlsh2)	🟢 done	271d78448, 300de974, c475fb86
CLI	aeroftp dedupe --similarity non-identical supports distance tuning. Default mode stays exact for back-compat	🟢 done	271d78448
GUI	The Find Duplicates dialog exposes Exact / Non-identical mode and shows similarity distance without preselecting similar files for deletion	🟢 done	d3c732269, f5199c909
Agent tools	local_find_duplicates delegates to the shared engine and returns similarity plus optional distance; aeroftp_dedupe and remote_dedupe support non-identical staging while preserving the remote exact SHA-256 fast path	🟢 done	300de974, c475fb86

Verified green: cargo fmt --all -- --check, cargo clippy --tests -- -D warnings, cargo build, the dedicated TLSH test dedupe::tests::non_identical_other_detects_tlsh_similar_bytes (1 passed), full cargo test outside sandbox (lib 2660 passed, 10 ignored; CLI 462 passed; integration, tool parity and doc tests green), and cargo audit clean.

[axpnet]

AeroCrypt default-salt portability and TSV marker migration are complete

Post-4.1.4 follow-up, shipped on main, shipping in v4.1.5 (#276, requested by @EhudKirsh).

AeroCrypt now has the owner-approved rclone-parity portability path without changing the default: random per-vault salt stays default, while default-salt mode is an advanced opt-in with a strength gate and explicit attestation. The headed marker path now writes the lean hidden .aerocrypt.tsv, keeps a read-both window for legacy .aeroftp-crypt.json, and exposes a verified manual migration path in both CLI and GUI.

Area	Description	Status	Ref
Default-salt mode	Added fixed default-salt support with strength selection, password entropy gating, explicit user attestation, and salt-mode MAC binding so metadata tampering fails closed	🟢 done	c7ff673a, 979c7fb7, 78daa525, 4b0b6c8e
Marker format	New headed vaults write .aerocrypt.tsv; parsers and provider paths read both TSV and legacy .aeroftp-crypt.json, including compare/headerless salt validation	🟢 done	fe0a9914, 5533c955, 73ee7786, 9f5745da
Migration	Added CLI crypt migrate-marker and a GUI Convert marker action that verifies legacy credentials, writes and reads back the TSV marker, checks the MAC, then deletes the legacy marker only after verification	🟢 done	9f5745da
Recovery kit and i18n	Added QR export controls and error-correction labels in both kit surfaces, softened keep-apart wording, and completed all locale strings with zero placeholders	🟢 done	8e4e4a29, eca764cc, 9f5745da
CI hardening	Linux Tauri build now retries transient AppImage helper download failures before failing the release job	🟢 done	9f5745da

Verified green: cargo fmt --all -- --check, cargo check --all-features, cargo clippy --all-targets -- -D warnings, cargo clippy --bin aeroftp-cli -- -D warnings, npm run typecheck, npm run build, npm run i18n:validate (46/46 locales, 0 placeholders), cargo test --package aeroftp --lib -- --test-threads=1 aerocrypt (53 passed), cargo test --package aeroftp --lib crypt_compare::tests -- --nocapture (9 passed), and cargo test --bin aeroftp-cli aerocrypt_metadata_migration_round_trip_leaves_aecr_bytes_unchanged (1 passed).

[axpnet]

Password Forge and encrypted-provider credential hardening are complete

Post-4.1.4 follow-up, shipped on main, shipping in v4.1.5 (#266, #369, requested by @EhudKirsh).

Security Tools is now a first-class utility in every theme, and Password Forge can generate credentials for real provider constraints instead of offering one all-or-nothing symbol set. The same CSPRNG-backed generator is available at the password creation points where AeroFTP users need it, while stored second-factor secrets for client-side-encrypted providers no longer receive primary-path prominence.

Area	Description	Status	Ref
Password Forge	Added Balanced, Maximum and reusable Compatible 32 presets, granular symbol groups, custom and excluded characters, a require-each-selected-group guarantee, ambiguous-character filtering, batch generation, passphrase mode and live entropy feedback	🟢 done	eccf8f4b
Inline generation	Security Tools is visible outside the Cyber theme, and compact generate controls with progress and success states now fill matching password fields in AeroVault, AeroCrypt, rclone crypt, Cryptomator and protected archive creation flows	🟢 done	eccf8f4b
Credential hardening	Filen and MEGA stored TOTP secrets now live in an advanced disclosure collapsed by default, with one-time codes kept as the primary path and a warning that storing the seed places both factors in the vault. Filen local WebDAV/S3 credential fields enforce the 32-character cap and rejected-character rules	🟢 done	eccf8f4b
Legacy and documentation	MD5 and SHA-1 are labelled legacy, and the provider integration guide documents credential scope, the limits of vault-at-rest protection, and least-privilege local bridge or MEGAcmd alternatives for Filen, MEGA and Internxt	🟢 done	eccf8f4b
Internationalization	All new controls, warnings, validation and preset text are complete across 46 non-English locales with no missing, orphaned or placeholder keys	🟢 done	eccf8f4b

Verified green: cargo fmt --manifest-path src-tauri/Cargo.toml --all -- --check, npm run typecheck, npm run build, targeted Vitest coverage (6 passed), Password Forge Rust coverage (4 passed), npm run i18n:validate (46/46 locales, 0 errors, 0 warnings, 0 placeholders), the pre-existing concurrent socket test passed on isolated retry, and live Tauri GUI verification covered Password Forge presets, generated character guarantees, collapsed 2FA disclosure, Filen constraints and AeroVault inline generation.

[axpnet]

Emergency Kit validity check and headed-marker safety net

Post-4.1.4 follow-up, shipped on main, shipping in v4.1.5 (#276, requested by @EhudKirsh).

Two complementary recovery-kit tracks from the same #276 thread are now on main: you can re-check a saved kit offline against the active profile keystore without a recovery drill, and a headed vault whose remote marker was deleted is rebuilt from the local keystore with a clear lockout warning instead of silently falling back to headerless unlock.

Area	Description	Status	Ref
Shared verify engine	Kit text, QR payload (AEROCRYPT-KIT v1), .aerocrypt.tsv and legacy .aeroftp-crypt.json parse into a public field report (vault ID, salt, version, KDF). Offline, no password, no secrets in output	🟢 done	3e78f1e8
CLI	aeroftp-cli crypt kit-verify --profile NAME --kit ./kit.txt (also --kit-text, optional remote headed-marker probe). Exit 0 match / 4 mismatch. agent-info crypt syntax refreshed	🟢 done	3e78f1e8
GUI Recovery Kit	Verify action, native Save/Print (Tauri dialog + iframe print), profile-slug default filename, draggable non-dismissive modal, info vs legacy-upgrade notices	🟢 done	3e78f1e8
Missing headed marker	Headed intent (withHeader) + missing remote marker + keystore config: restore via stage/verify/rename, one-shot warning. Intentional headerless never auto-heals	🟢 done	3e78f1e8
Legacy JSON → TSV	Opt-in Convert marker on the AEROCRYPT badge menu only when a legacy JSON marker remains (no nag on connect). Marker ops peel to the raw transport under an active overlay. New headed creates still write .aerocrypt.tsv only	🟢 done	3e78f1e8
Pre-Tier-1 kits	Connect-time keystore backfill can add a vault_id-ready public config so Recovery kit works after one connect without rewriting the remote until the user converts	🟢 done	3e78f1e8

Verified green: cargo test --lib aerocrypt::emergency_kit (11 passed), cargo test --lib crypt_overlay_provider (57 passed, including headed restore + headerless no-write), cargo clippy --lib --tests -- -D warnings, cargo clippy --bin aeroftp-cli -- -D warnings, live GUI checks (Filen convert + kit save/print/verify match, Koofr kit after connect, Convert only when JSON remains).

[axpnet]

v4.1.5 batch: CLI env-var ergonomics, classic-rsync live progress, PLACES focus refetch, CI/i18n hygiene

Post-4.1.4 follow-up, done on main, shipping in v4.1.5.

Six commits landed on main (3e78f1e8..a8cafd12): two CLI ergonomics changes, a delta-transfer UX fix, a Windows/macOS PLACES sidebar responsiveness fix, and two hygiene commits that put the fmt gate and the 46-locale translations back to green.

Area	Description	Status	Commit
CLI	AEROFTP_MACHINE truthy env var enables machine mode (equivalent to --machine), resolved right after argument parsing; AEROFTP_NO_BANNER realigned to strict_env_truthy, so =0 and =false no longer suppress the banner	🟢 done	1bbe7d59, e98dbcbc
Delta transfer	the classic-rsync path forwards live --info=progress2 progress to the UI sink, so a transfer animates instead of jumping at the final summary; the stdout loop was extracted into a unit-tested helper	🟢 done	98632670
AeroFile	the PLACES sidebar refetches mounted volumes and unmounted partitions on window focus, so a drive attached in the background appears without waiting for the 30s Windows/macOS poll (lighter mitigation of the #351 hotplug idea; Linux already updates instantly)	🟢 done	4da7a3dd
Hygiene	cargo fmt on the aerocrypt kit-verify hunks that 3e78f1e8 left unformatted (fixes the red Checks fmt gate on main); aerocryptNative.legacyMarkerConvertAction translated into all 46 non-EN locales	🟢 done	d32a76a8, a8cafd12

Verified green locally: cargo fmt --check, cargo clippy --all-targets -D warnings (plus --bin aeroftp-cli and --all-features --tests), vitest (434 tests), tsc --noEmit, i18n:validate (47 locales, 0 placeholders), and the affected rsync/delta module tests. CI is running on all platforms; the previously red Checks fmt gate is expected green now.

[axpnet]

Transfer queue survives an app restart (TQ-7a backend journal)

Post-4.1.4 follow-up, done on main, shipping in v4.1.5.

The transfer queue was in-memory only, so an app restart lost every queued and in-flight item. TQ-7a adds the backend half: a journal that persists the queue and detects what was interrupted. The frontend restore that shows and re-queues those items is the next slice (TQ-7b), and per-provider byte-range resume stays deferred (TQ-7c).

Area	Description	Status	Commit
Transfer queue	new transfer_queue_journal module mirroring the SyncJournal pattern: re-executable descriptors (direction, local and remote path, profile id, size, status, attempts, last error) written atomically to aeroftp_data_root/transfer-queue/queue.json under a write lock, with load, clear, and an interrupted-entries query (returns Pending / InProgress / Failed, never Completed or Cancelled)	🟢 done	f5f1b9be
Command surface	three thin Tauri commands (save, load, clear) registered in the handler; a missing journal loads as None so first run is unchanged; profile_id is Option<String> so saved profiles and ad-hoc quick-connect are both representable	🟢 done	f5f1b9be

Scope, as specified: persistence and restart detection only, no byte-range resume, no auto-reconnect on startup, no frontend wiring, no changes to the batch executors.

Gates green (automated): cargo fmt, cargo clippy --bin aeroftp-cli --all-features -D warnings and --all-features --tests -D warnings, cargo test (5 new journal unit tests on a TempDir, plus the existing suite). Verified structurally on review: diff isolated to the new module and the lib.rs command registration, no scope creep.

[axpnet]

Interrupted transfers are restored on the next launch (TQ-7b)

Post-4.1.4 follow-up, done on main, shipping in v4.1.5.

TQ-7a persisted the queue to a journal; TQ-7b closes the loop on the frontend. An interrupted transfer now comes back after a restart and can be re-run, so a crash, a quit, or a lost connection mid-queue no longer loses the pending work.

Area	Description	Status	Commit
Persist	the queue is written to the journal on change (debounced), joining a side map of per-item local, remote, and profile descriptors and mapping the UI statuses (staged/pending/transferring/completed/error) to the journal statuses	🟢 done	42935d65
Restore	on startup the journal is loaded, terminal items are dropped, and each still-pending or in-flight item is re-queued as a "Restored" item (badge plus Retry) without auto-starting or auto-reconnecting; download re-run drives the normal path, upload re-run uses an explicit remote directory from the journal	🟢 done	42935d65
i18n	two new keys (transfer.restored, transfer.restoredHint) translated into all 46 non-EN locales	🟢 done	42935d65

Verified live end to end on a real SFTP server: enqueued 100 MB uploads, killed the app mid-flight, relaunched (the two interrupted transfers reappeared as pending "Restored" items, the completed ones correctly did not), reconnected, and Retry re-uploaded them for real with live progress. Gates green: typecheck, vitest (448 tests), i18n:validate (47 locales, 0 placeholders), 14 new unit tests for the pure helpers.

Follow-up noted from the same live test: the per-item Retry is not very discoverable, so a startup resume prompt is queued under Requested (row 10).

[axpnet]

v4.1.5 is released ✅

AeroFTP v4.1.5 is out: release notes.

All 12 patches queued above shipped in this release: non-identical duplicate detection across the engine, GUI, CLI and agent tools, a transfer queue that survives an app restart (backend journal plus frontend restore of interrupted transfers), AeroCrypt default-salt portability with the shared .aerocrypt.tsv marker and verified migration, an offline Emergency Kit validity check, a missing headed marker rebuilt from the local keystore, Password Forge and encrypted-provider credential hardening, a live classic-rsync progress bar, and PLACES volume refetch on window focus. All 47 languages at 100 percent. Published on all platforms (Linux deb/rpm/AppImage/Snap, Windows MSI and setup exe, macOS x64 and aarch64 dmg), every asset Sigstore-signed. AUR bumped to 4.1.5.

This tracker is now closed. Known issues reported against v4.1.5 and patches landing on main for the next release move to the new tracker: #1414 (AeroFTP 4.1.6). The still-open Requested / under consideration rows have been carried over there.

Thanks @EhudKirsh for the reports and discussions behind this release.