Troubleshooting

This guide covers common issues when integrating the Intents Swap Widget.

If you can't find an answer here, please open an issue or reach out to the team.

Table of Contents

• Balance Loading Issues

• Dependency Conflicts

• Wallet Connection Problems

• Configuration Errors

Balance Loading Issues

Balances load infinitely

Causes & Solutions:

1. Missing API key - The widget will try to use a set of RPCs by default, but Alchemy is more reliable and you can have better control with Alchemy API key.

   <SwapWidget
     alchemyApiKey="your-alchemy-api-key"
     // ...other props
   />

2. API rate limits - Alchemy free tier has request limits. Check your Alchemy dashboard for quota usage.

3. TON balances not loading - TON requires a separate API key.

   <SwapWidget
     tonCenterApiKey="your-toncenter-api-key"
     // ...other props
   />

4. RPC endpoint issues - The widget retries failed RPC calls twice before giving up. If balances still fail, check network connectivity and RPC availability.

Dependency Conflicts

Conflicting package versions

Cause: The widget uses several libraries that your project may also use. When versions differ, bundlers may include multiple versions causing conflicts.

Solution: Add resolutions to your package.json to lock versions, example:

"resolutions": {
  "valtio": "2.1.7",
  "valtio-fsm": "1.0.0",
  "@noble/curves": "^1.6.0",
  "@noble/hashes": "^1.5.0",
  "strip-ansi": "6.0.1",
  "@reown/appkit": "1.8.17",
  "@reown/appkit-common": "1.8.17",
  "@reown/appkit-controllers": "1.8.17",
  "@reown/appkit-pay": "1.8.17",
  "@reown/appkit-polyfills": "1.8.17",
  "@reown/appkit-scaffold-ui": "1.8.17",
  "@reown/appkit-ui": "1.8.17",
  "@reown/appkit-utils": "1.8.17",
  "@reown/appkit-wallet": "1.8.17",
  "@solana/addresses": "5.5.1",
  "@solana/codecs-core": "5.5.1",
  "@solana/errors": "5.5.1",
  "@solana/keys": "5.5.1"
}

For Yarn, resolutions work as shown above. For npm or bun, use overrides instead:

"overrides": {
  "valtio": "2.1.7"
}

Please refer to your package manager documentation for ways of doing this:

• npm

• yarn

• pnpm

Wallet Connection Problems

Wallet not connecting

Solutions:

1. Check provider configuration - Ensure you're passing the correct provider for your account type:

   // For EVM wallets
   providers={{ evm: window.ethereum }}
   
   // For Solana wallets
   providers={{ sol: solanaWallet }}
   
   // For Stellar wallets
   providers={{ stellar: stellarWallet }}
   
   // For NEAR wallets
   providers={{ near: () => nearWallet }}

2. Add the matching network plugin - For EVM, Solana, and Stellar swaps, you also need to install the relevant sibling package and register its network plugin via the plugins property.

   import { evm } from '@aurora-is-near/intents-swap-widget-evm';
   import { sol } from '@aurora-is-near/intents-swap-widget-solana';
   import { stellar } from '@aurora-is-near/intents-swap-widget-stellar';
   
   <WidgetConfigProvider
     config={{
       plugins: { evm, sol, stellar },
       // ...
     }}
   >

Errors like No EVM transfer configured mean the plugin is missing:

Note that NEAR is built into widget core and does not need a plugin.

1. Verify walletSupportedChains - We will attempt to establish the supported chains based on the format of the wallet address, however, you may want to include chains your wallet supports:

   walletSupportedChains={['eth', 'base', 'arb']}

Configuration Errors

No styles/broken design

Cause: Missing CSS imports.

Solution: Import required CSS files:

import '@aurora-is-near/intents-swap-widget/styles.css';

Check our detailed theming documentation.

Tailwind & CSS reset

If you use global CSS reset e.g.:

*, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; }

It will break widget's styles due to Tailwind layering system. If you face that issue and see no paddings, margins or other style issues in a widget please scope your CSS resetting styles with a @layer base as below:

@layer base {
  *, *::before, *::after {
    box-sizing: border-box;
    margin: 0;
    padding: 0;
  }
}

Still Having Issues?

If this guide didn't solve your problem:

1. Check the GitHub Issues for similar problems

2. Open a new issue with:

   • Widget version

   • Your configuration (remove sensitive keys)

   • Error messages from the console

   • Steps to reproduce