MetaMask / MetaMask/connect-monorepo
Safari iOS address is invalid
- Dominant language
- TypeScript
- Stars
- 12
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
I'm using "wagmi": "^3.6.0" and "@metamask/connect-evm": "^0.9.0".
```
createConfig({
chains: [baseSepolia],
ssr: true,
multiInjectedProviderDiscovery: false,
transports: {
[baseSepolia.id]: http(),
},
connectors: [
metaMask({
dapp: {
name: 'xxx',
url: 'xxx',
iconUrl: `xxx`,
},
}),
],
storage: createStorage({
storage: cookieStorage,
}),
})
```
When calling `signMessage`, `sendCalls` or `writeContract` from wagmi's hooks, I'm sometimes getting safari popup "Safari cannot open the page because the address is invalid".
In chrome for iOS it's working 100% of the time.
In chrome desktop it's working 100% of the time, but it's using metamask browser extension instead of iOS native app obviously.
Maybe related: https://github.com/MetaMask/metamask-sdk/issues/1042
Contributor guide
Research direction
No repository files or tests are identified in the report. Start by reproducing the intermittent failure on Safari iOS with the shown wagmi configuration, focusing on signMessage, sendCalls, and writeContract; compare it with Chrome iOS and the related MetaMask SDK issue. Done means identifying the invalid address cause and confirming the affected calls work reliably on Safari iOS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100