@bobfrankston/rmfmail 1.1.79 → 1.1.81

package/.commitmsg

@@ -1,14 +1,20 @@
-Fix user-dictionary persistence; correct contacts.md
-
-User dictionary never reached the server: mailxapi.js (the desktop IPC
-bridge) had no getUserDict/addUserDictWord methods, so api-client's
-optional-chained calls silently no-op'd — added words lived only in
-localStorage. Added the four bridge methods, a bulk addUserDictWords
-RPC, and a load-time reconcile in spellcheck.ts that pushes any
-localStorage-only words up to userdict.csv so accumulated words are
-recovered.
-
-contacts.md: removed the stale `discovered` documentation — since Q150
-the discovered set is a per-device local cache and is not written to or
-synced via contacts.jsonc. Documented the cloud file as preferred +
-denylist + groups (+ preserved hand-added keys).
+Fix spurious attachment-open error + blocking alert that stalled sync
+
+Three faults behind "failed to open" appearing after the file had
+actually opened in Acrobat:
+
+1. The openAttachment IPC call used the default 30s ceiling. A cold
+   parse worker (14-25s) plus a 1.7 MB PDF blew past it, so the client
+   rejected even though the service succeeded. getAttachment/
+   openAttachment now get a 120s ceiling in mailxapi.js.
+
+2. On that spurious rejection the viewer ran the browser-only blob
+   fallback, whose atob() threw "string not correctly encoded". The
+   fallback now runs ONLY when openAttachment returns undefined (real
+   browser / --server mode); a genuine IPC failure is reported, not
+   retried via blob.
+
+3. The failure was shown with window.alert() — a modal that freezes the
+   WebView event loop, stalling IPC event delivery so sync looked
+   stopped. Replaced with a non-blocking banner via a mailx-alert
+   CustomEvent handled by app.ts showAlert().

package/client/android-bootstrap.bundle.js

@@ -6253,6 +6253,11 @@ ${bodyEncoded}`;
   async getAttachment(_accountId, _uid, _attachmentId, _folderId) {
     return this.notImpl("getAttachment");
   }
+  // Android opens attachments via the native bridge (_nativeBridge.openAttachment),
+  // not this service path — getAttachment + base64 hand-off covers it.
+  async openAttachment(_accountId, _uid, _attachmentId, _folderId) {
+    return this.notImpl("openAttachment");
+  }
   // Spam / abuse
   async markAsSpamMessages(_accountId, _uids) {
     return this.notImpl("markAsSpamMessages");