@bounded-sh/client 0.0.112 → 0.0.114

package/dist/{index-BmNNZlTl.js → index-BZ0X1Z9X.js}

@@ -3817,6 +3817,46 @@ function looksLikeSolanaMobileWallet(name) {
 function solanaMobileWalletLeavesPage(name) {
     return name === LOCAL_MOBILE_WALLET_NAME;
 }
+/**
+ * Whether this wallet answers a sign-in from its authorization cache, so the
+ * cached record must be dropped before asking it to sign in.
+ *
+ * Both Mobile Wallet Adapter transports consult their persisted authorization
+ * before EVERY authorize call, including the one that carries the Sign In With
+ * Solana payload (@solana-mobile/wallet-standard-mobile 0.5.3
+ * lib/esm/index.browser.js:1291). A record left by a plain connect holds no
+ * sign-in result, so that sign-in fails with "no sign in result returned by
+ * wallet" without the wallet app ever being asked; a record left by an earlier
+ * sign-in holds that OLD proof, so a later sign-in replays a spent nonce. The
+ * wallet's own `standard:disconnect` clears the record locally - it opens
+ * nothing - and the sign-in that follows then authorizes afresh, with its
+ * payload, in the wallet app. A name check, like leavesPage: this describes the
+ * transport, and the same adapter registered by another SDK behaves the same.
+ */
+function solanaMobileWalletAnswersSignInFromCache(name) {
+    return mobileWalletNames.has(name);
+}
+/**
+ * The Wallet Standard name of a feature a Mobile Wallet Adapter account reports.
+ *
+ * The adapter copies a wallet app's per-account `features` into the Wallet
+ * Standard account untranslated (0.5.3 lib/esm/index.browser.js:1421), and the
+ * MWA protocol names them differently from the Wallet Standard (spec feature
+ * identifiers: `solana:signMessages`, `solana:signInWithSolana`,
+ * `solana:signTransactions`). Filtered by the Wallet Standard names, such an
+ * account looks unable to sign a message or sign in, and the page sees no
+ * connected account after a successful authorization. Wallet Standard names pass
+ * through unchanged, so this applies to every account.
+ */
+const MWA_FEATURE_NAMES = {
+    'solana:signMessages': 'solana:signMessage',
+    'solana:signInWithSolana': 'solana:signIn',
+    'solana:signTransactions': 'solana:signTransaction',
+};
+function walletStandardFeatureName(feature) {
+    var _a;
+    return (_a = MWA_FEATURE_NAMES[feature]) !== null && _a !== void 0 ? _a : feature;
+}
 /**
  * Register Solana Mobile's MWA wallet with the Wallet Standard registry so
  * wallet discovery surfaces it. Idempotent - the first wallet-lane activation
@@ -6311,7 +6351,7 @@ async function getAuthProvider(config, fromStorage = false) {
             // manager as legacy email sessions. Human login should be started
             // with loginWithRedirect(); this provider is kept as the restore and
             // logout surface for those sessions.
-            currentAuthProvider = new (await Promise.resolve().then(function () { return require('./email-auth-provider-CyFsnSzx.js'); })).EmailAuthProvider();
+            currentAuthProvider = new (await Promise.resolve().then(function () { return require('./email-auth-provider-DeORQbTK.js'); })).EmailAuthProvider();
             break;
         case "phantom": {
             // First-class Solana WALLET LOGIN (the poof/TaroBase-style "connect
@@ -6353,7 +6393,7 @@ async function getAuthProvider(config, fromStorage = false) {
             // (bounded-login-widget.ts), so registration never counts as
             // evidence the user has a wallet.
             await ensureSolanaMobileWalletRegistered(config, configuredNetwork);
-            const { InjectedWalletProvider } = await Promise.resolve().then(function () { return require('./injected-wallet-provider-D8vIsUHf.js'); });
+            const { InjectedWalletProvider } = await Promise.resolve().then(function () { return require('./injected-wallet-provider-B9jvzDM5.js'); });
             currentAuthProvider = new InjectedWalletProvider(resolveInjectedWalletConfig(config), rpcUrl, configuredNetwork);
             break;
         }
@@ -6366,7 +6406,7 @@ async function getAuthProvider(config, fromStorage = false) {
             // Selecting authMethod:'evm-wallet' IS the opt-in — pass evmWalletConfig
             // to point at a specific wallet or set chainId/domain.
             const evmWalletConfig = ((_a = config.evmWalletConfig) !== null && _a !== void 0 ? _a : {});
-            const { InjectedEvmWalletProvider } = await Promise.resolve().then(function () { return require('./injected-evm-wallet-provider-C8YItSiB.js'); });
+            const { InjectedEvmWalletProvider } = await Promise.resolve().then(function () { return require('./injected-evm-wallet-provider-D06arDQD.js'); });
             currentAuthProvider = new InjectedEvmWalletProvider(evmWalletConfig);
             break;
         }
@@ -6391,7 +6431,7 @@ async function getAuthProvider(config, fromStorage = false) {
             break;
         case "guest":
             // Anonymous auth: a device-local ed25519 keypair signs the challenge.
-            currentAuthProvider = new (await Promise.resolve().then(function () { return require('./guest-auth-provider-B4WIWOjV.js'); })).GuestAuthProvider();
+            currentAuthProvider = new (await Promise.resolve().then(function () { return require('./guest-auth-provider-5bX-xt6K.js'); })).GuestAuthProvider();
             break;
     }
     if (!currentAuthProvider) {
@@ -6453,7 +6493,7 @@ async function signInAnonymously() {
     // Lazy-load the guest provider so its ed25519/web3 dependencies stay out of
     // the main bundle for data-only apps. Specifier is a static string literal
     // so bundle-splitting can see it.
-    const provider = new (await Promise.resolve().then(function () { return require('./guest-auth-provider-B4WIWOjV.js'); })).GuestAuthProvider();
+    const provider = new (await Promise.resolve().then(function () { return require('./guest-auth-provider-5bX-xt6K.js'); })).GuestAuthProvider();
     setAuthLoading(true); // reflect "signing in…" while the guest keypair session is minted
     // adoptSessionProvider awaits only getConfig() (already resolved here) and then
     // runs every write - provider/method/config/marker/user - in one synchronous
@@ -6624,7 +6664,7 @@ function ensureSharedWalletLoginReady() {
     if (!sharedWalletReady) {
         sharedWalletReady = (async () => {
             await core.getConfig();
-            await Promise.resolve().then(function () { return require('./injected-wallet-provider-D8vIsUHf.js'); });
+            await Promise.resolve().then(function () { return require('./injected-wallet-provider-B9jvzDM5.js'); });
         })().catch((error) => {
             sharedWalletReady = null;
             throw error;
@@ -6727,7 +6767,7 @@ async function loginWithWallet(options) {
         await ensureSharedWalletLoginReady();
     else
         await ensureWalletLoginReady();
-    const { InjectedWalletProvider } = await Promise.resolve().then(function () { return require('./injected-wallet-provider-D8vIsUHf.js'); });
+    const { InjectedWalletProvider } = await Promise.resolve().then(function () { return require('./injected-wallet-provider-B9jvzDM5.js'); });
     // Keep the RAW wallet provider: the offchain wrapper forwards only a fixed
     // set of methods, so cleanup below must speak to the provider that actually
     // holds the config rather than to whatever is wrapping it.
@@ -7617,7 +7657,9 @@ function standardWalletToInjectedProvider(wallet, configuredNetwork) {
     // mobile adapter fills DEFAULT_FEATURES in exactly that case. So an empty list
     // means none, and reading it as "everything" picks an account that cannot sign
     // and fails at the wallet instead of here.
-    const accountSupports = (account, feature) => account.features.includes(feature);
+    // The mobile adapter hands a wallet app's own feature names through
+    // untranslated, so each name is read as its Wallet Standard equivalent.
+    const accountSupports = (account, feature) => account.features.some((f) => walletStandardFeatureName(f) === feature);
     const pickSolanaAccount = (accounts) => {
         // With a network configured, an account that does not support it is not a
         // usable account: `WalletAccount.chains` is what that account can sign for,
@@ -7692,13 +7734,23 @@ function standardWalletToInjectedProvider(wallet, configuredNetwork) {
         } }, (hasFeature(wallet, SolanaSignIn)
         ? {
             async signIn(input) {
-                const acc = requireAccount();
-                if (!accountSupports(acc, SolanaSignIn))
-                    throw new Error("Wallet account does not support solana:signIn");
+                var _a;
                 const sign = feature(wallet, SolanaSignIn);
                 if (!sign)
                     throw new Error("Wallet does not support solana:signIn");
+                const open = currentAccount();
+                if (open && !accountSupports(open, SolanaSignIn))
+                    throw new Error("Wallet account does not support solana:signIn");
+                if (solanaMobileWalletAnswersSignInFromCache(wallet.name)) {
+                    // Drop the cached authorization so this sign-in is performed by the
+                    // wallet app, with its payload, rather than answered from a record
+                    // that holds no sign-in result or an earlier sign-in's spent nonce.
+                    // Local to the page: the adapter's disconnect opens nothing.
+                    await ((_a = feature(wallet, StandardDisconnect)) === null || _a === void 0 ? void 0 : _a.disconnect());
+                }
                 const [out] = await sign.signIn(input);
+                if (!out)
+                    throw new Error("Wallet returned no sign-in result");
                 return { account: { address: out.account.address }, signedMessage: out.signedMessage, signature: out.signature };
             },
         }
@@ -8869,11 +8921,13 @@ async function prepareAndOpen(opts, pending) {
             card.appendChild(foot);
             return card;
         };
-        // Solana Mobile leaves the page to sign: connecting spends the tap that
-        // started login, so requesting the signature straight afterwards runs with
-        // no transient activation left, Chrome blocks the `solana-wallet:` intent
-        // navigation, and the protocol reports the wallet as missing. Collect a
-        // second tap on its OWN view - never by adding a listener to a button that
+        // Solana Mobile leaves the page to sign in: the nonce fetch that precedes
+        // the sign-in outlives the tap that started login, so requesting the
+        // sign-in straight afterwards runs with no transient activation left,
+        // Chrome blocks the `solana-wallet:` intent navigation, and the protocol
+        // reports the wallet as missing. Collect a fresh tap on its OWN view (one
+        // wallet trip: sign-in authorizes and signs in the same step, there is no
+        // connect before it) - never by adding a listener to a button that
         // already starts a login, which would run both handlers on that tap and
         // kick off a duplicate login beside the one waiting for the gesture.
         // Injected wallets sign in-page and get no extra step.
@@ -11442,4 +11496,4 @@ exports.useAuth = useAuth;
 exports.useBuildRun = useBuildRun;
 exports.useQuery = useQuery;
 exports.waitForAuthReady = waitForAuthReady;
-//# sourceMappingURL=index-BmNNZlTl.js.map
+//# sourceMappingURL=index-BZ0X1Z9X.js.map