[bug]: Connection to Sei Chain not possible.

[Crismon96]

Description

I am building a SeiEvm react-native app. We are also already hosting a Web-App that successfully integrates reowns appkit with the same chain configuration.

I have integrated the library like described in the docs and I am being prompted to my wallet and redirected after accepting the connection. I also see my address displayed in the AppKitButton. Still my logs show several errors after attempting the connection and const { address, isConnected, chainId } = useAppKitAccount(); is not resolved to a connected state.

The Error:

Error: 15:22:52 | ERROR : Wallet Error 
{
  "error": "Required wallet components missing",
  "stack": "Error: Required wallet components missing\n    at ?anon_0_ (address at /private/var/containers/Bundle/Application/

Just before that I see one more potentially useful log.

JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)

This is how I initialize appkit:

import "@walletconnect/react-native-compat";
import {
  createAppKit,
  defaultConfig,
  AppKit,
} from "@reown/appkit-ethers-react-native";

// 3. Define your chains
const mainnet = {
  chainId: 1329,
  name: 'Sei Network',
  currency: "SEI",
  explorerUrl: "https://seitrace.com",
  rpcUrl: "https://evm-rpc.sei-apis.com",
  nativeCurrency: { name: 'Sei', symbol: 'SEI', decimals: 18 },
  rpcUrls: {
    default: {
      http: ['https://evm-rpc.sei-apis.com/'],
      webSocket: ['wss://evm-ws.sei-apis.com/'],
    },
  },
  blockExplorers: {
    default: {
      name: 'Seitrace',
      url: 'https://seitrace.com',
      apiUrl: 'https://seitrace.com/pacific-1/api',
    },
  },
  contracts: {
    multicall3: {
      address: '0xcA11bde05977b3631167028862bE2a173976CA11',
    },
  },
};

const chains: Parameters<typeof createAppKit>[0]['chains'] = [mainnet];

// 4. Create modal
createAppKit({
  projectId,
  metadata,
  chains,
  config,
  enableAnalytics: true, // Optional - defaults to your Cloud configuration
});


export function WalletConnectProvider({ children }: { children: React.ReactNode }) {
  return <>
  <AppKit />
  {children}
  </>
}

AppKit SDK version

"@reown/appkit-ethers-react-native": "1.3.1", "@walletconnect/react-native-compat": "2.21.8",

Output of npx react-native info

System:
OS: macOS 15.3.2
CPU: (8) arm64 Apple M2
Memory: 145.58 MB / 16.00 GB
Shell:
version: 3.2.57
path: /bin/bash
Binaries:
Node:
version: 20.13.1
path: /private/var/folders/77/xk_dk18j35d3qlpn53s8z7dw0000gn/T/xfs-0b7c9e9f/node
Yarn:
version: 3.5.1
path: /private/var/folders/77/xk_dk18j35d3qlpn53s8z7dw0000gn/T/xfs-0b7c9e9f/yarn
npm:
version: 10.5.2
path: ~/.nvm/versions/node/v20.13.1/bin/npm
Watchman:
version: 2025.08.25.00
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.16.2
path: /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 24.5
- iOS 18.5
- macOS 15.5
- tvOS 18.5
- visionOS 2.5
- watchOS 11.5
Android SDK: Not Found
IDEs:
Android Studio: 2025.1 AI-251.26094.121.2513.14007798
Xcode:
version: 16.4/16F6
path: /usr/bin/xcodebuild
Languages:
Java:
version: 17.0.16
path: /usr/bin/javac
Ruby:
version: 3.4.5
path: /opt/homebrew/opt/ruby/bin/ruby
npmPackages:
"@react-native-community/cli":
installed: 20.0.2
wanted: ^20.0.2
react:
installed: 19.0.0
wanted: 19.0.0
react-native:
installed: 0.79.5
wanted: 0.79.5
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: true
iOS:
hermesEnabled: true
newArchEnabled: true

Expo Version (if applies)

53

Steps to reproduce

Integrate the the library exactly as described in docs. Build for production. Try to connect to Sei Mainnet (see above configuration).

Snack, code example, screenshot, or link to a repository

https://blkswn-studio.sentry.io/share/issue/0b638866bf9a4f72938d2a243093a86e/

[Crismon96]

@ignaciosantise Actually it might be related to this issue: #347
When I use Compass Wallet instead of Metamask I was able to connect and sign a TX. This is not possible with MM going the exact same route.
Unfortunatly using MM is kinda important to us since its basically 80% of our users. Can you roll the solution from the linked issue to the ethers6 integration bundle too?

[ignaciosantise]

hey @Crismon96 👋 im about to release a full refactor of the SDK, and it already covers the case were Metamask returns the wrong chain.

If you want to try it now, here are the docs: https://reown-5552f0bb-chore-rn-multichain.mintlify.app/appkit/react-native/core/installation

and the migration docs too -> https://reown-5552f0bb-chore-rn-multichain.mintlify.app/appkit/react-native/core/migration-multichain

as you are only using Ethers, it should be easy to upgrade

[Crismon96]

@ignaciosantise Nice that you are supplying it so quickly. I went forward and tried to migrate. Unfortunatly I got stuck:

1. The EVM chains to not work for me. With the below setup code I get the following error in both cases when: I want to intialize with EthMainnet and SeiMainnet (both definitions imported from viem). Even when manually adjusting the definitions for type errors I still get:

WARN Please use proxy object ERROR TypeError: Cannot convert undefined value to object, js engine: hermes
on createAppKit call.

Example code:

import { sei, mainnet } from "viem/chains";

// 1. Get projectId from https://dashboard.reown.com
const projectId = <mycustomid>;
// 2. Create config
const metadata = {
  name: 'Apollon',
  description: 'AppKit for Apollon',
  url: 'https://app.apollon.fi', // origin must match your domain & subdomain
  icons: ['https://app.apollon.fi/assets/svgs/Apollon_logo_negative.svg'],
  redirect: {
    native: "apollon://",
  },
};

// 3. Define your chains
const seiMainnet = {
  id: 1329,
  name: 'Sei Network',
  nativeCurrency: { name: 'Sei', symbol: 'SEI', decimals: 18 },
  rpcUrls: {
    default: {
      http: ['https://evm-rpc.sei-apis.com/'],
      webSocket: ['wss://evm-ws.sei-apis.com/'],
    },
  },
  blockExplorers: {
    default: {
      name: 'Seitrace',
      url: 'https://seitrace.com',
      apiUrl: 'https://seitrace.com/pacific-1/api',
    },
  },
  contracts: {
    multicall3: {
      address: '0xcA11bde05977b3631167028862bE2a173976CA11',
    },
  },
 // I have added these manually as the type required it.
  chainNamespace: 'eip155' as any,
  caipNetworkId: "eip155:1329" as '`${string}:${string}`',
  testnet: false
};

// 1. Define your AppKitNetworks (for AppKit's UI and network management)
// These can come from viem/chains (for EVM) or be custom AppKitNetwork objects.
const appNetworks: AppKitNetwork[] = [
  mainnet // viem chains are automatically compatible as AppKitNetwork for 'eip155'
  
  // None of these 3 EVM chains work and all result in the described error.
  // sei, from viem
  // seiMainnet manually declared with added fields required by type
];

const ethersAdapter = new EthersAdapter();

// 4. Create modal
export const appKit = createAppKit({
  projectId,
  metadata,
  networks: appNetworks, // Master list of networks for AppKit UI and context
  adapters: [
    ethersAdapter,  // Handles EVM chains defined in 'networks'
  ],
  // This isnt defined in the main docs.
  storage: MMKVStorage,
});

2. The storage config option isnt documented in the main docs you have linked. An example is visible if the user drills down into config options docs with an example. This example doesnt use the @react-native-async-storage/async-storage package though that is recommended with the main installation. It would be helpful if the required param is also in the main docs with an example that matches the package that is recommended for installs, maybe a working storage config can be exported from the base package to make things easier. Using the exampe storage solution did not solve issue 1. above

[ignaciosantise]

@Crismon96

1. I think you might be having an issue with multiple version packages in your node_modules.
   Can you add this to your package.json and install the deps again?

// if you use YARN:  
"resolutions": {
    "@walletconnect/ethereum-provider": "2.21.8",
    "@walletconnect/universal-provider": "2.21.8",
    "valtio": "2.1.8",
    "viem": "2.37.4"
  },

// if you use NPM
  "overrides": {
    "@walletconnect/ethereum-provider": "2.21.8",
    "@walletconnect/universal-provider": "2.21.8",
    "valtio": "2.1.8",
    "viem": "2.37.9"
  },

2. The storage option is documented here and there's a link to a sample. I could also add an example for AsyncStorage

And async-storage is still needed despite is not being used because one of the internal dependencies still imports it, so if you don't install it, it will break. Im still discussing with the team on how to solve this properly

[Crismon96]

Nice, the error is gone now. I am doing a prod build, lets see if this solves my issue.

I think having a default storage solution with AsyncStorage (if you decide to keep it as a peer dependency for the base package) would be the ideal case. The dev doesnt need additional dependencies that way and could just import a default that way or the storage param could be optional.

[ignaciosantise]

Okey, let me know how it goes!

I think having a default storage solution with AsyncStorage

It was the default solution, but a lot of people is migrating to other solutions, that's why im trying to make it generic, in the future i'll completely remove async-storage so its fully generic

[Crismon96]

@ignaciosantise So I took 2 steps forward and 1 step back. When I connect via MM now I am being prompted to "Switch network".
If I select the "Sei Network" I get "Failed to fetch transactions" and nothing happens.

In my logger I can see that isConnected is true and chainId is 1329 which is exactly what I expect. This also happens if I only give permissions for Sei mainnet during the sign process of the wallet.

For another wallet "Compass" (Seis "native" EVM wallet) I do not get that "Switch Network" prompt and everything seems to work fine.

[ignaciosantise]

Can you upload a video of the failed to fetch error? It shouldn’t block the network switch

[ignaciosantise]

@Crismon96 apart from that error, are you able to switch to Sei and continue the flow? We'll solve Failed to fetch transactions issue, its on our side

[Crismon96]

ScreenRecording_10-01-2025 12-35-17_1.MP4.zip

@ignaciosantise Thanks for being so responsive btw. Github wouldnt let me upload the MP4 so I had to compress it.

To me it seems because isConnected is true, as well as the chainId correct and the provider is there that we might be in a success state. But only on MM it detects the network as "wrong" and as soon as I close the "Switch Network" modal I am being disconnected. Therefore I can go forward with MM at the moment. Can you reproduce the issue with MM locally? If not let me know and I can provide you my MM version or try some other wallets myself. As mentioned everything works just fine with "Compass" wallet.

[Crismon96]

I encountered another issue that I think is reown related. When I restart my production app again after first usage of a fresh install by Apps UI stalls after the Splash screen. This happened on multiple prod builds and only happens if I connected successfully with reown before (Without connection I could repeaditly use the app).

As this seems to be related to having a previous connection and an error during the initialization I tried to run a custom development build.

When I try to connect any wallet I just get:

 WARN  Connection failed: [Error: WalletConnectConnector: Provider not initialized. Call init() first.]
 WARN  Sentry Logger [warn]: Possible Unhandled Promise Rejection (id: 20):
[object Object]

Can you hint me what adjustments I have to make to be able to connect during a custom iOS development build on my physical phone? Do I have to adjust the redirect scheme or something else?
I would like to provide you with some specific JS error due to why the app stalls after connection and restart. Is this problem known to you or reproducible on your end?

[ignaciosantise]

Hey @Crismon96 thanks for the clear descriptions! I'll look into this today.
Regarding the first error, i'll try to repro locally with MM to see what is happening.

Regarding the second one, is this log Connection failed: [Error: WalletConnectConnector: Provider not initialized. Call init() first.] happening on your production build? Are you using useProvider hook?

Can you confirm the steps to repro?

1. Connect to a wallet successfully
2. Close the app completely
3. Reopen the app
4. Does it restore the connection? Or do you try to connect again?
5. Connection failed: [Error: WalletConnectConnector: Provider not initialized. Call init() first.] ?

Can you upload a video of this case?