[bug] Fireblocks wallet listing declares mobile deep link scheme (fireblocks-wc://) that the Fireblocks app does not handle — wallet-specific QR is unscannable

[skotancilar]

Link to minimal reproducible example

No custom code is needed — this reproduces with the wallet listing data served by the WalletConnect/Reown Explorer registry itself:

https://explorer-api.walletconnect.com/v3/wallets?projectId=YOUR_PROJECT_ID&search=fireblocks

The Fireblocks entry (5864e2ced7c293ed18ac35e0db085c09ed567d67346ccb6f58a0327a75137489) declares:

"mobile": {
  "native": "fireblocks-wc://",
  "universal": null
}

Any AppKit setup that surfaces the Fireblocks wallet reproduces it, e.g. the official Vue + Wagmi example from https://github.com/reown-com/appkit-web-examples with:

createAppKit({
  adapters: [wagmiAdapter],
  networks,
  projectId,
  metadata,
  featuredWalletIds: ["5864e2ced7c293ed18ac35e0db085c09ed567d67346ccb6f58a0327a75137489"]
})

We can provide a screen recording on request.

Steps to Reproduce

1. Open an AppKit modal that lists the Fireblocks wallet (e.g. via featuredWalletIds above).
2. On desktop, click the Fireblocks tile. AppKit renders a wallet-specific QR code, which wraps the pairing URI in the registry-declared deep link scheme: fireblocks-wc://wc?uri=<encoded wc: uri>.
3. Scan that QR with a phone camera (iOS or Android) that has the current Fireblocks mobile app installed (iOS: https://apps.apple.com/us/app/fireblocks/id1439296596, Android: com.fireblocks.client).

Summary

Expected: the OS recognizes the fireblocks-wc:// scheme and opens the Fireblocks app with the pairing URI, as with other wallets' deep-link QR codes.

Actual: the OS reports "There aren't any apps on your phone that can use the info in this QR code." The current Fireblocks mobile app does not register the fireblocks-wc:// URL scheme, so every wallet-specific QR generated from this registry entry is unscannable. Fireblocks' supported connection flows are scanning a raw wc: URI QR from inside the app (its Web3 connections scanner) and the web console (https://console.fireblocks.io/v2/) — the generic WalletConnect QR path in AppKit works fine with the in-app scanner.

Impact: users who pick the Fireblocks tile hit a dead end and assume the dApp is broken. As a dApp we have no way to fix this on our side other than hiding the Fireblocks listing via excludeWalletIds, which is what we've done as a workaround.

Ask: please verify the Fireblocks listing's mobile deep link with the wallet vendor and either fix the scheme or remove the mobile deep link from the listing (so AppKit falls back to flows that work). Filing here since the registry data is Reown-hosted and listing changes go through your wallet-listing process; we are reporting the same issue to Fireblocks separately.

List of related npm package versions

• @reown/appkit 1.8.8
• @reown/appkit-adapter-wagmi 1.8.8
• @wagmi/core 2.21.2
• viem 2.37.9
• vue 3.5.22

(Not AppKit-version-specific — the QR content is driven by the registry entry.)

Node.js Version

v22.20.0

Package Manager

npm@10.9.3

[linear]

REOWN-4798