ChatApp

byGalax/ChatApp

Fork 0

Commit Graph

Author	SHA1	Message	Date
byGalax	f9e1d2f073	fix(secure-store): preserve original ciphertext on decrypt failure + startup path log Critical hotfix for the 0.17.0 regression: users upgrading from 0.16.x were logged out, and their next login wrote a fresh empty secure-store on top of the original ciphertext — destroying device keys irrecoverably. Why it happened: loadState used a blanket `catch {}` that conflated "file doesn't exist (genuine new user)" with "file exists but can't be decrypted (DPAPI / OSCrypt quirk after the install rename)". Both paths returned an empty Map; the next scheduledSave then overwrote the original .bin file with a fresh blob. Fix: * Separate ENOENT from decrypt/parse failures. ENOENT → empty Map. Any other read error → log, empty Map (no quarantine, matches old behaviour for transient lock issues). * When decrypt/parse fails the original file is renamed to <file>.broken-<iso-ts> BEFORE returning empty Map. The next save writes to a fresh file; the original ciphertext is preserved on disk so a future build (or manual recovery) can still get at the bytes. * Loud console.error around the failure so future regressions surface in main-process logs. main.ts: move setPath('userData', appData/ChatApp) BEFORE setName so any productName-derived path caching inside setName can't beat us to it. Add a startup log of the resolved paths so future debugging has hard evidence instead of guessing. Affected users on 0.17.0 should still recover via Settings → Backup Wiederherstellen (account-level keys are unchanged); this fix prevents the data destruction for anyone who hasn't upgraded yet. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-12 21:54:14 +02:00
byGalax	825160ee46	feat(desktop): port v0.11.4-v0.15.2 from Tauri to Electron + Discord-parity audio (v0.16.0) Chronological port of every Tauri release commit (v0.11.4 -> v0.15.2) into the Electron rebuild, plus Discord-style audio handling that goes beyond the Tauri original. Highlights: - All 17 Tauri release commits ported (audio fixes, custom notification sound, Discord-style chat UX, profile banner, changelog page, Discord-parity call UX, screen-share echo + re-watch UX, audio-loop fix). - Native napi-rs audio-loopback addon with WASAPI process-loopback: * EXCLUDE_TARGET_PROCESS_TREE for full-screen shares -> peers never hear themselves echoed back through the capture. * INCLUDE_TARGET_PROCESS_TREE for window shares -> only the picked window's audio is captured, not the whole OS mixer (Discord parity). * HWND -> PID resolution via Win32 GetWindowThreadProcessId. - Discord-style screen-source picker (thumbnail grid, screens vs apps tabs, live-refreshing thumbnails). - Hash routing fix for packaged builds (file:// can't resolve BrowserRouter paths). - Tauri sources removed (apps/desktop/src-tauri). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-06 23:35:01 +02:00

Author

SHA1

Message

Date

byGalax

f9e1d2f073

fix(secure-store): preserve original ciphertext on decrypt failure + startup path log

Critical hotfix for the 0.17.0 regression: users upgrading from 0.16.x
were logged out, and their next login wrote a fresh empty secure-store
on top of the original ciphertext — destroying device keys irrecoverably.

Why it happened: loadState used a blanket `catch {}` that conflated
"file doesn't exist (genuine new user)" with "file exists but can't be
decrypted (DPAPI / OSCrypt quirk after the install rename)". Both paths
returned an empty Map; the next scheduledSave then overwrote the
original .bin file with a fresh blob.

Fix:
* Separate ENOENT from decrypt/parse failures. ENOENT → empty Map. Any
  other read error → log, empty Map (no quarantine, matches old
  behaviour for transient lock issues).
* When decrypt/parse fails the original file is renamed to
  <file>.broken-<iso-ts> BEFORE returning empty Map. The next save
  writes to a fresh file; the original ciphertext is preserved on disk
  so a future build (or manual recovery) can still get at the bytes.
* Loud console.error around the failure so future regressions surface
  in main-process logs.

main.ts: move setPath('userData', appData/ChatApp) BEFORE setName so
any productName-derived path caching inside setName can't beat us to
it. Add a startup log of the resolved paths so future debugging has
hard evidence instead of guessing.

Affected users on 0.17.0 should still recover via Settings → Backup
Wiederherstellen (account-level keys are unchanged); this fix prevents
the data destruction for anyone who hasn't upgraded yet.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-12 21:54:14 +02:00

byGalax

825160ee46

feat(desktop): port v0.11.4-v0.15.2 from Tauri to Electron + Discord-parity audio (v0.16.0)

Chronological port of every Tauri release commit (v0.11.4 -> v0.15.2)
into the Electron rebuild, plus Discord-style audio handling that goes
beyond the Tauri original.

Highlights:
  - All 17 Tauri release commits ported (audio fixes, custom notification
    sound, Discord-style chat UX, profile banner, changelog page,
    Discord-parity call UX, screen-share echo + re-watch UX, audio-loop
    fix).
  - Native napi-rs audio-loopback addon with WASAPI process-loopback:
      * EXCLUDE_TARGET_PROCESS_TREE for full-screen shares -> peers
        never hear themselves echoed back through the capture.
      * INCLUDE_TARGET_PROCESS_TREE for window shares -> only the
        picked window's audio is captured, not the whole OS mixer
        (Discord parity).
      * HWND -> PID resolution via Win32 GetWindowThreadProcessId.
  - Discord-style screen-source picker (thumbnail grid, screens vs
    apps tabs, live-refreshing thumbnails).
  - Hash routing fix for packaged builds (file:// can't resolve
    BrowserRouter paths).
  - Tauri sources removed (apps/desktop/src-tauri).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-06 23:35:01 +02:00

2 Commits