@bobfrankston/rmfmail 1.2.37 → 1.2.39

package/client/android-bootstrap.bundle.js

@@ -10770,6 +10770,40 @@ function installBridge() {
   const api = {
     isApp: true,
     platform: "android",
+    // Link / contact / calendar handoff to native apps. On Android THIS
+    // object is window.mailxapi — NOT client/lib/mailxapi.js — so the
+    // openExternal there never ran on the phone, and this object had no
+    // openExternal at all, so app.ts fell through to window.open() (a no-op
+    // in the WebView). That's why preview links / the LinkedIn "View message"
+    // button did nothing even after the mailxapi.js fixes (Bob 2026-06-18,
+    // proven by the [android-link] trace stopping at "parent got linkClick").
+    // We're definitively on the Android host here, so just navigate the top
+    // frame to the mailxapi-intent:// scheme that MainPage.xaml.cs intercepts.
+    openExternal: (url) => {
+      if (!url) return;
+      try {
+        console.log("[android-link] android-api openExternal \u2192 intent " + url);
+        window.location.href = "mailxapi-intent://open/" + encodeURIComponent(url);
+      } catch (e) {
+        console.error("[android-link] openExternal failed", e);
+      }
+    },
+    openContact: (email) => {
+      if (!email) return;
+      try {
+        window.location.href = "mailxapi-intent://contact/" + encodeURIComponent(email);
+      } catch (e) {
+        console.error("openContact failed", e);
+      }
+    },
+    openCalendarEvent: (htmlLink) => {
+      if (!htmlLink) return;
+      try {
+        window.location.href = "mailxapi-intent://calendar/" + encodeURIComponent(htmlLink);
+      } catch (e) {
+        console.error("openCalendarEvent failed", e);
+      }
+    },
     getAccounts: () => service.getAccounts(),
     getFolders: (accountId) => service.getFolders(accountId),
     getMessages: (accountId, folderId, page, pageSize) => service.getMessages(accountId, folderId, page, pageSize),