fix(sdk-api): keep browser v1 decrypt to SJCL

modules/sdk-api/src/encrypt.ts

@@ -1,7 +1,7 @@
 import * as sjcl from '@bitgo/sjcl';
 import { randomBytes } from 'crypto';
 
-import { decryptV1 } from './decryptV1';
+import { decryptV1, parseV1Envelope } from './decryptV1';
 import { decryptV2, encryptV2 } from './encryptV2';
 
 /**
@@ -76,6 +76,15 @@ function isIterCapViolation(err: unknown): boolean {
   return err instanceof Error && /iter:\s*expected integer|iter out of range/i.test(err.message);
 }
 
+/**
+ * True in window and worker runtimes. Used to route browser v1 decrypt
+ * straight to SJCL instead of through the Node-oriented `native` path, whose
+ * `crypto-browserify` AES-CCM has been reported not to work in a real browser.
+ */
+function isBrowserRuntime(): boolean {
+  return typeof window !== 'undefined' || typeof self !== 'undefined';
+}
+
 /**
  * v1 decrypt with an SJCL safety net.
  *
@@ -98,6 +107,15 @@ export async function decryptV1WithFallback(
   ciphertext: string,
   native: (pw: string, ct: string) => Promise<string> = decryptV1
 ): Promise<string> {
+  if (isBrowserRuntime()) {
+    try {
+      parseV1Envelope(ciphertext);
+    } catch (parseErr) {
+      if (isIterCapViolation(parseErr)) throw parseErr;
+      // Any other parse rejection (e.g. absent `v`) is a shape SJCL still accepts.
+    }
+    return sjcl.decrypt(password, ciphertext);
+  }
   try {
     return await native(password, ciphertext);
   } catch (nativeErr) {