-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug]: linkMode not working after connecting wallet #301
Comments
hey @putti-johnnie 👋 Which version of MetaMask are you using? Are you using the latest? Also, does the redirect work in Trust Wallet? |
@ignaciosantise Yes, I am using the latest MetaMask from AppStore. Maybe I missed some config? Do I need any additional setup in the project dashboard except the iOS Bundle IDs? |
@putti-johnnie maybe your project doesn't have deep-links enabled. Here's the official guide to enable them: https://reactnative.dev/docs/linking#enabling-deep-links |
@ignaciosantise hmm... I am pretty sure the unniversal link is working on iOS. I have other feature working with universal link. |
@putti-johnnie the config seems okey 🤔 can you provide a fresh project where i can repro the issue? |
@ignaciosantise I can try to prepare a fresh project. Meanwhile, could you please check my other issue? |
@putti-johnnie you can use import { useAccount } from 'wagmi';
...
const { address } = useAccount(); |
Description
Actually, there are 2 issues:
const { data: walletClient } = useWalletClient();
to monitor the wallet status, but it doesn't get updated once the wallet is connected.As you can see from the attached video, once I go back to my app manually, it doesn't show the address until I refresh the entire app.
BTW, I can confirm the universal link is working properly.
AppKit SDK version
"@reown/appkit-wagmi-react-native": "^1.1.1",
Output of
npx react-native info
Expo Version (if applies)
"expo": "~52.0.25"
Steps to reproduce
await open(); // from const { open } = useAppKit()
Snack, code example, screenshot, or link to a repository
wagmi config:
video:
ScreenRecording_01-17-2025.19-48-08_1.mov
The text was updated successfully, but these errors were encountered: