​
Browser requests fail with CORS

Open the KeyWay developer console and register the exact origin, including scheme and port. Confirm that the provider uses that application’s public appId. This is KeyWay API configuration, not a Stytch dashboard requirement.

​
SharedArrayBuffer or WASM startup fails

Check that the page sends:
Then verify window.crossOriginIsolated === true. Browser extensions or third-party resources without compatible cross-origin resource policy headers can also break isolation. This requirement applies only to nodeMode="browser". Managed mode, the default from SDK 0.0.7, does not load Fiber WASM in the consuming page.

​
An active device lease is required

In browser mode, the account’s Fiber lease expired or another device took it. Call connect() again. Avoid running the same account’s channels concurrently in multiple browser profiles.

​
Fiber wallet is bound to another device

In browser mode, another browser still holds the Fiber lease, or the previous browser did not complete an explicit logout and encrypted backup. Log out on the active device before moving the account.

​
A payment has no route

The public graph did not contain a route with enough outbound liquidity for the requested amount.
  • Try a smaller payment.
  • Confirm both sender and receiver have ready public channels.
  • Allow a newly opened channel time to propagate through gossip.
  • Keep browser-mode nodes online while testing; managed nodes persist after logout.

​
CKB balance updates slowly

CKB does not store an account balance field. The SDK asks an indexer to sum live cells for the account’s lock script. Faucet and newly mined cells may appear after an indexing delay.

​
Channel activation takes time

Activation includes peer connection, collaborative funding construction, user confirmation, Lit authorization, CKB transaction broadcast, and on-chain confirmation. Use the progress callback to show the current stage rather than presenting one indefinite loading state.

​
Supported scope

The current package supports CKB testnet, CKB-funded Fiber channels, invoices, routed payments, and encrypted state handoff after explicit logout. Mainnet, UDT payments, unexpected-close backup, and self-hosted KeyWay infrastructure are not supported.