fix(sdk): mobile wallet UX fixes and connection stability

[akbarsaputrait]

Summary

Fixes several mobile wallet UX issues, primarily around Phantom/Backpack deeplink flows and connection stability.

Changes

Connection fixes

• Force EVM connect on deeplink open: When a dual-chain wallet (Phantom, Backpack) opens via deeplink, only Solana auto-connects via wallet-standard. SDK now silently triggers connect() for the matching injected EVM connector — wallet approves inside its own browser, no user prompt needed. Matched by Solana wallet name, not hardcoded to Phantom.
• dualChainConnect flag not cleared: After Phantom connects both chains, the flag was never cleared. Subsequent wallet connections (e.g. MetaMask) triggered the dual-chain handler again and looped back to SELECT_METHOD instead of SELECT_TOKEN. Fixed by moving the clear inside the route-guarded effect.

State race fix

• Atomic route state: RozoPayProvider was setting route and routeMeta as two separate setState calls. After an await (disconnect sequence), this created a two-render window where guards read stale route, causing 'Pay with another wallet' click to do nothing. Combined into a single setState.

Disconnect safety

• disconnectAll(): Extracted shared helper in SelectMethod using Promise.allSettled with isSolanaConnected/isStellarConnected guards. Fixes TypeError: r.disconnect is not a function when Solana wallet adapter is uninitialized (Phantom deeplink, Solana-only connected).

UX improvements

• Pay to Address loading: Replaced 'Loading...' subtitle text with a spinner in the right-icon slot while deposit address options fetch.
• Connector error states: ConnectorSolana and ConnectorStellar now show Connection Failed with Try Again and Cancel buttons instead of a silent hang (e.g. WalletConnect proposal expired).

Schema

• Added sourceAmountUnits and sourceTokenSymbol optional fields to zRozoPayOrderMetadata in pay-common.

Testing

• Build clean, pay-common 35/35 tests pass
• Lint exits 0

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
intent-example	Error		Jul 17, 2026 9:57am

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0adee842fd

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[shawnmuggle]

Review — mobile wallet UX fixes

Solid direction overall: the userDisconnected guard, disconnectAll() via Promise.allSettled, the atomic route+routeMeta state, and the Try Again / Cancel error states are all real fixes. One functional regression I'd want addressed before merge, plus two smaller nits.

🟠 P1 — Force-EVM-connect races the auto-navigation on Phantom/Backpack deeplink

RozoPayModal/index.tsx

On a mobile deeplink open, Solana connects first via wallet-standard (isSolanaConnected = true, isEthConnected = false). The new force-EVM effect only fires an async connect() — it doesn't set dualChainConnect and doesn't block navigation.

In that same render, the SELECT_METHOD auto-navigation effect sees isSolanaConnected && !isEthConnected && solanaPaymentEligible && !disableMobileInjector (default disableMobileInjector = false) and immediately routes to the Solana SELECT_TOKEN screen. By the time EVM silently connects, route is no longer SELECT_METHOD / a connect page, so the dual-chain branch never runs — and the user never sees the dual-wallet selection this PR is meant to show. They get pulled into the single-chain Solana flow instead. Deterministic race, hits the most common Phantom path.

Fix: set dualChainConnect = true (or introduce a pending state) before firing the EVM connect(), and have the auto-nav effect hold off on the Solana single-chain jump while that flag is set / EVM is still settling.

🟡 P2 — "Try Again" on Solana connect error may hang on the spinner

Pages/Solana/ConnectorSolana/index.tsx

Try Again does disconnect().then(() => select(solanaConnector)) with the same connector. @solana/wallet-adapter treats select() of the already-selected wallet as a no-op, so it won't necessarily re-initiate the connection. The error clears and the spinner comes back (loading = !isConnected && !connectionError), but the connect may never actually re-fire — leaving the user stuck on the spinner. Prefer an explicit connect() (extract a retryConnect()) rather than relying on re-selecting the same connector.

🟡 P2 — setUserDisconnected(false) cleared before the order-ready early return

Pages/MobileConnectors/index.tsx — handleDeeplinkWallet

setUserDisconnected(false) runs before the if (!orderReady) return guard. Tapping while the deeplink order is still hydrating clears the "user explicitly disconnected" flag without actually starting a connection — so if Phantom/Backpack then silently reconnects, the modal's auto-route effect can drag the user back into the old wallet flow. Move the flag reset below the orderReady / deeplink-config validation so it's only cleared when a connection actually begins.

---

_{Note on the two earlier automated flags — both are non-issues: the "lockfile not updated" P1 was against an earlier commit (0adee842); pnpm-lock.yaml has since been bumped and the connectkit @rozoai/intent-common specifier now matches package.json at 0.1.25, so a frozen-lockfile install is fine. The "OptionsList icon order regression" is a false positive — both IconStackContainer and RightIconStackContainer are position: absolute (left:20px / right:20px), so DOM order doesn't affect visual placement.}

[shawnmuggle]

Reviewed the full diff — no P0. The mobile UX fixes are sound: userDisconnected flag to stop auto-reconnect from re-routing after an explicit disconnect, disconnectAll() via Promise.allSettled with connected-guards (fixes r.disconnect is not a function), atomic route+routeMeta state (fixes the two-render race), and the Solana/Stellar connector Try Again / Cancel recovery.

⚠️ Merge-coordination required — this PR overlaps 9 files with #47 (RozoPayModal, SelectMethod, RozoPayProvider, PayContext, ConnectorSolana, ConnectorStellar, ConnectorList, OptionsList, rozoPay.ts), and both target master. This PR is effectively an iteration of the same mobile-UX work in #47:

• Force-EVM-connect: #47 hardcodes isPhantom() + connectors.find(c => c.type === 'injected') (first injected); this PR generalizes to match by solanaWallet.adapter.name. This one is the better approach.
• userDisconnected guard exists here, not in #47.

They cannot be merged independently — whichever lands second will conflict heavily and may re-introduce the older approach. Recommend deciding an order (land this UX approach, rebase/drop the duplicate in #47) or folding them together.

P2 (non-blocking): the force-EVM match c.name.toLowerCase().includes(solanaName) is a substring match — a short wallet name could in theory match an unrelated injected connector. Low risk, but an exact-name match would be safer.

Approving on the UX logic; please resolve the #47 overlap before/at merge.