> For the complete documentation index, see [llms.txt](https://docs.intents.aurora.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intents.aurora.dev/intents-swap/widget-configuration/troubleshooting.md).
# Troubleshooting
This guide covers common issues when integrating the Intents Swap Widget.
If you can't find an answer here, please [open an issue](https://github.com/aurora-is-near/intents-swap-widget/issues) 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.
```tsx
```
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.
```tsx
```
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:
```json
"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:
```json
"overrides": {
"valtio": "2.1.7"
}
```
Please refer to your package manager documentation for ways of doing this:
* [npm](https://docs.npmjs.com/cli/v9/configuring-npm/package-json#overrides)
* [yarn](https://classic.yarnpkg.com/lang/en/docs/selective-version-resolutions/)
* [pnpm](https://pnpm.io/9.x/package_json#resolutions)
### Wallet Connection Problems
#### Wallet not connecting
**Solutions:**
1. **Check provider configuration** - Ensure you're passing the correct provider for your account type:
```tsx
// 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.
```tsx
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';
```
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:
```tsx
walletSupportedChains={['eth', 'base', 'arb']}
```
### Configuration Errors
#### No styles/broken design
**Cause:** Missing CSS imports.
**Solution:** Import required CSS files:
```tsx
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.:
```css
*, *::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:
```css
@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](https://github.com/aurora-is-near/intents-swap-widget/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
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.intents.aurora.dev/intents-swap/widget-configuration/troubleshooting.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.