Status wallet fails to request permission when using createModernProviderInterface
See original GitHub issueI did a bisect and looks like it broken in-between v1.14.0 and v1.15.0.
When I change Status’ interface from:
provider && getProviderName(provider) === 'Status'
? createModernProviderInterface(provider)
: null
to:
interface: {
name: 'Status',
connect: () => provider.enable(),
address: {
get: () => getAddress(provider)
},
network: {
get: () => getNetwork(provider)
},
balance: {
get: () => getBalance(provider)
},
}
it works flawlessly again.
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Frequently Asked Questions
Status messenger does not use one central server to and from which ... DApps must ask permission to view and use your wallet...
Read more >EIP-2255: Wallet Permissions System
This provides a standard interface for requesting permissions and checking a domain's current permissions status.
Read more >The Seal of Approval: Know What You're Consenting To ...
This involves giving the dapp permission to retrieve your wallet address, and is a prerequisite for interacting with the platform.
Read more >How can I revoke token approvals and permissions on ...
Navigate through the ERC-20, ERC-721, or ERC-1155 tabs until you see the token approval you would like to revoke. Press Revoke to revoke...
Read more >Issue #2255 · ethereum/EIPs - Web3 Wallet Permissions
This provides a standard interface for requesting permissions and checking a domain's current permissions status.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@chuckbergeron This is fixed in version
1.19.1
via PR #491. Thanks @flexsurfer for your help on this one!Ok sweet that should be an easy fix, will take a look and see if we can get this sorted out soon. Thanks!