Unable to connect to Fuel Wallet in UI

TypeScript SDK
1

When trying to select the wallet in the UI, it asks me to install the wallet but I already have it installed.

Screenshot 2024-02-13 at 4.44.30 PM
Screenshot 2024-02-13 at 4.44.30 PM760Ă—808 22.3 KB

1 Like
2

Already installed:

Screenshot 2024-02-13 at 4.45.47 PM
Screenshot 2024-02-13 at 4.45.47 PM2272Ă—134 12.8 KB

3

Try to clean cache and remove cookies of your browser ?

1 Like
4

@tommaay What version of the wallet SDK are you using? The official wallet is currently at version 0.13.10. If you are using a version of the SDK that is ahead of that, you’ll need to use a development wallet until the official extension is upgraded (happening soon!).

If you are going through the beta-5 quickstart, you can use the development wallet extension.

2 Likes
5

Nope I did try that and it didn’t work.

6

Hey Sara that’s the issue then I am using fuel wallet version "^0.15.2". So for beta-5, I will need to set my fuelup and wallet cli tools to use beta 5?

7

Hi @tommaay yes to use version 0.15.2 of the wallet SDK you should also be using the latest toolchain in fuelup, and version 0.73.0 of the fuels TypeScript SDK.

Then you can select Fuel Wallet Development in the wallet connect UI.

8

Hey @sarah thanks I am able to update and switch to the latest toolchain but I am not able to switch my forc wallet to beta-5 using the cli. Is there a way to do this?

EDIT
Ok I got it to deploy. I got confused by the error messages when trying to deploy my contract to beta-5. It said to go to the beta-4 faucet to get some funds so I thought it was on beta-4 but there was a specific link to request funds for the wallet for beta-5 testnet.

And issue I am having is trying to import the wallet created with the CLI into Fuel Wallet using the private key. I was able to do it for the Fuel Wallet which is on Beta-4 but not the Fuel Development Wallet on Beta-5. It says the private key is not valid when trying to import it.

EDIT 2
Ok I was able to import the cli address into the development wallet using the private key but had to prepend it with 0x. Not sure if this is a bug or not but just wanted to give that info.

1 Like
9

bro, have you solved it? I get the same problem as you

10

image
image776Ă—620 17.3 KB

Installed but unable to connect，need help
my env:
beta-5， 0.73.0 fuels sdk， 0.15.2 wallet sdk

11

image

12

hi sarah, i already try your suggestion. but no luck. wallet ex still not detected.
im using
“@fuel-wallet/react”: “0.13.10”,
“@fuel-wallet/sdk”: “^0.13.10”,
“fuels”: “>=0.67.0”,

13

@Idekubaguscom, the current wallet has since been upgraded to 0.15.2. Try using that version of the wallet sdks, and version 0.73.0 of fuels for the beta-5 testnet.

14

Hi @sarah,

I’m facing the same issue, apparently either Main/Dev wallet is detected:

image
image1837Ă—818 35.6 KB

Dev Wallet Version: 0.21.3
MainWallet Version: 0.21.3

These are the dependencies:

{
  "name": "template-nextjs",
  "version": "0.1.3",
  "private": true,
  "scripts": {
    "prebuild": "fuels build",
    "fuels:dev": "fuels dev",
    "dev": "next dev",
    "build": "pnpm run prebuild && next build",
    "start": "next start",
    "lint": "next lint"
  },
  "dependencies": {
    "@fuels/connectors": "^0.2.2",
    "@fuels/react": "^0.18.1",
    "fuels": "0.89.1",
    "@tanstack/react-query": "^5.29.2",
    "dotenv": "^16.4.5",
    "next": "14.2.2",
    "react": "^18.2",
    "react-dom": "^18.2",
    "react-hot-toast": "^2.4.1",
    "react-use": "^17.5.0"
  },
  "devDependencies": {
    "@types/node": "^20",
    "@types/react": "^18.2",
    "@types/react-dom": "^18.2",
    "autoprefixer": "^10.0.1",
    "eslint": "^8",
    "eslint-config-next": "14.0.1",
    "postcss": "^8",
    "tailwindcss": "^3.3.0",
    "typescript": "^5"
  }
}
15

Hey @eesheng,

What version of fuels did you bootstrap this application with?

The following changes might guide you into fixing this issue - this was addressed as of v0.89.2.

1 Like