Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / airgap-it/beacon-sdk issues and pull requests
#260 - Temple is not detected correctly on Firefox
Issue -
State: closed - Opened by Necroskillz over 3 years ago
- 3 comments
Labels: bug
#260 - Temple is not detected correctly on Firefox
Issue -
State: open - Opened by Necroskillz over 3 years ago
- 2 comments
Labels: bug
#260 - Temple is not detected correctly on Firefox
Issue -
State: open - Opened by Necroskillz over 3 years ago
- 2 comments
Labels: bug
#260 - Temple is not detected correctly on Firefox
Issue -
State: closed - Opened by Necroskillz over 3 years ago
- 3 comments
Labels: bug
#260 - Temple is not detected correctly on Firefox
Issue -
State: open - Opened by Necroskillz over 3 years ago
- 2 comments
Labels: bug
#260 - Temple is not detected correctly on Firefox
Issue -
State: open - Opened by Necroskillz over 3 years ago
- 2 comments
Labels: bug
#260 - Temple is not detected correctly on Firefox
Issue -
State: closed - Opened by Necroskillz over 3 years ago
- 3 comments
Labels: bug
#260 - Temple is not detected correctly on Firefox
Issue -
State: open - Opened by Necroskillz over 3 years ago
- 2 comments
Labels: bug
#260 - Temple is not detected correctly on Firefox
Issue -
State: closed - Opened by Necroskillz over 3 years ago
- 3 comments
Labels: bug
#260 - Temple is not detected correctly on Firefox
Issue -
State: open - Opened by Necroskillz over 3 years ago
- 2 comments
Labels: bug
#260 - Temple is not detected correctly on Firefox
Issue -
State: open - Opened by Necroskillz over 3 years ago
- 2 comments
Labels: bug
#260 - Temple is not detected correctly on Firefox
Issue -
State: open - Opened by Necroskillz over 3 years ago
- 2 comments
Labels: bug
#258 - Allow disabling of wallets in Beacon
Issue -
State: closed - Opened by burk3 over 3 years ago
- 6 comments
Labels: enhancement
#258 - Allow disabling of wallets in Beacon
Issue -
State: open - Opened by burk3 over 3 years ago
- 5 comments
Labels: enhancement
#258 - Allow disabling of wallets in Beacon
Issue -
State: closed - Opened by burk3 over 3 years ago
- 6 comments
Labels: enhancement
#258 - Allow disabling of wallets in Beacon
Issue -
State: closed - Opened by burk3 over 3 years ago
- 6 comments
Labels: enhancement
#258 - Allow disabling of wallets in Beacon
Issue -
State: closed - Opened by burk3 over 3 years ago
- 6 comments
Labels: enhancement
#258 - Allow disabling of wallets in Beacon
Issue -
State: closed - Opened by burk3 over 3 years ago
- 6 comments
Labels: enhancement
#258 - Allow disabling of wallets in Beacon
Issue -
State: closed - Opened by burk3 over 3 years ago
- 6 comments
Labels: enhancement
#258 - Allow disabling of wallets in Beacon
Issue -
State: closed - Opened by burk3 over 3 years ago
- 6 comments
Labels: enhancement
#258 - Allow disabling of wallets in Beacon
Issue -
State: open - Opened by burk3 over 3 years ago
- 5 comments
Labels: enhancement
#258 - Allow disabling of wallets in Beacon
Issue -
State: open - Opened by burk3 over 3 years ago
- 5 comments
Labels: enhancement
#256 - NextJS Bundle Analyser.
Issue -
State: closed - Opened by andrevenancio over 3 years ago
- 2 comments
Labels: bug
#256 - NextJS Bundle Analyser.
Issue -
State: closed - Opened by andrevenancio over 3 years ago
- 2 comments
Labels: bug
#256 - NextJS Bundle Analyser.
Issue -
State: closed - Opened by andrevenancio over 3 years ago
- 2 comments
Labels: bug
#243 - Feature: Add support for encrypt/decrypt messages
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement, future consideration
#243 - Feature: Add support for encrypt/decrypt messages
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement, future consideration
#243 - Feature: Add support for encrypt/decrypt messages
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement, future consideration
#243 - Feature: Add support for encrypt/decrypt messages
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement, future consideration
#243 - Feature: Add support for encrypt/decrypt messages
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement, future consideration
#243 - Feature: Add support for encrypt/decrypt messages
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement, future consideration
#243 - Feature: Add support for encrypt/decrypt messages
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement, future consideration
#243 - Feature: Add support for encrypt/decrypt messages
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement, future consideration
#223 - Add iframe based transport for web wallets
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement
#223 - Add iframe based transport for web wallets
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement
#223 - Add iframe based transport for web wallets
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement
#223 - Add iframe based transport for web wallets
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement
#223 - Add iframe based transport for web wallets
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement
#223 - Add iframe based transport for web wallets
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement
#223 - Add iframe based transport for web wallets
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement
#223 - Add iframe based transport for web wallets
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement
#213 - Allow operation details to be sent in the OperationResponse
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement, future consideration
#213 - Allow operation details to be sent in the OperationResponse
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement, future consideration
#213 - Allow operation details to be sent in the OperationResponse
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement, future consideration
#213 - Allow operation details to be sent in the OperationResponse
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: enhancement, future consideration
#208 - Custom RPC Node Sensing
Issue -
State: closed - Opened by sebuhbitcoin over 3 years ago
- 5 comments
Labels: enhancement, future consideration
#208 - Custom RPC Node Sensing
Issue -
State: closed - Opened by sebuhbitcoin over 3 years ago
- 5 comments
Labels: enhancement, future consideration
#208 - Custom RPC Node Sensing
Issue -
State: closed - Opened by sebuhbitcoin over 3 years ago
- 5 comments
Labels: enhancement, future consideration
#208 - Custom RPC Node Sensing
Issue -
State: closed - Opened by sebuhbitcoin over 3 years ago
- 5 comments
Labels: enhancement, future consideration
#208 - Custom RPC Node Sensing
Issue -
State: closed - Opened by sebuhbitcoin over 3 years ago
- 5 comments
Labels: enhancement, future consideration
#208 - Custom RPC Node Sensing
Issue -
State: closed - Opened by sebuhbitcoin over 3 years ago
- 5 comments
Labels: enhancement, future consideration
#208 - Custom RPC Node Sensing
Issue -
State: closed - Opened by sebuhbitcoin over 3 years ago
- 5 comments
Labels: enhancement, future consideration
#193 - Draggable warning
Issue -
State: closed - Opened by ungarson over 3 years ago
- 3 comments
Labels: enhancement
#193 - Draggable warning
Issue -
State: closed - Opened by ungarson over 3 years ago
- 3 comments
Labels: enhancement
#193 - Draggable warning
Issue -
State: closed - Opened by ungarson over 3 years ago
- 3 comments
Labels: enhancement
#193 - Draggable warning
Issue -
State: closed - Opened by ungarson over 3 years ago
- 3 comments
Labels: enhancement
#193 - Draggable warning
Issue -
State: closed - Opened by ungarson over 3 years ago
- 3 comments
Labels: enhancement
#193 - Draggable warning
Issue -
State: closed - Opened by ungarson over 3 years ago
- 3 comments
Labels: enhancement
#193 - Draggable warning
Issue -
State: closed - Opened by ungarson over 3 years ago
- 3 comments
Labels: enhancement
#193 - Draggable warning
Issue -
State: closed - Opened by ungarson over 3 years ago
- 3 comments
Labels: enhancement
#193 - Draggable warning
Issue -
State: closed - Opened by ungarson over 3 years ago
- 3 comments
Labels: enhancement
#193 - Draggable warning
Issue -
State: closed - Opened by ungarson over 3 years ago
- 3 comments
Labels: enhancement
#193 - Draggable warning
Issue -
State: closed - Opened by ungarson over 3 years ago
- 3 comments
Labels: enhancement
#193 - Draggable warning
Issue -
State: closed - Opened by ungarson over 3 years ago
- 3 comments
Labels: enhancement
#193 - Draggable warning
Issue -
State: closed - Opened by ungarson over 3 years ago
- 3 comments
Labels: enhancement
#193 - Draggable warning
Issue -
State: closed - Opened by ungarson over 3 years ago
- 3 comments
Labels: enhancement
#185 - Adding a peer before the p2p connection is ready will "ignore" the peer
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: bug
#180 - ClearActiveAccount does not work if called immediately after DAppClient instantiation
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
- 1 comment
Labels: bug
#180 - ClearActiveAccount does not work if called immediately after DAppClient instantiation
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
- 1 comment
Labels: bug
#180 - ClearActiveAccount does not work if called immediately after DAppClient instantiation
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
- 1 comment
Labels: bug
#180 - ClearActiveAccount does not work if called immediately after DAppClient instantiation
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
- 1 comment
Labels: bug
#175 - GetPermissions on WalletClient does not return all permissions
Issue -
State: open - Opened by AndreasGassmann over 3 years ago
Labels: bug
#175 - GetPermissions on WalletClient does not return all permissions
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: bug
#175 - GetPermissions on WalletClient does not return all permissions
Issue -
State: open - Opened by AndreasGassmann over 3 years ago
Labels: bug
#175 - GetPermissions on WalletClient does not return all permissions
Issue -
State: open - Opened by AndreasGassmann over 3 years ago
Labels: bug
#175 - GetPermissions on WalletClient does not return all permissions
Issue -
State: open - Opened by AndreasGassmann over 3 years ago
Labels: bug
#175 - GetPermissions on WalletClient does not return all permissions
Issue -
State: closed - Opened by AndreasGassmann over 3 years ago
Labels: bug
#170 - Building client with rollup and typescript results in incorrect call to qrcode module
Issue -
State: closed - Opened by fredcy almost 4 years ago
- 15 comments
Labels: bug
#170 - Building client with rollup and typescript results in incorrect call to qrcode module
Issue -
State: closed - Opened by fredcy almost 4 years ago
- 15 comments
Labels: bug
#170 - Building client with rollup and typescript results in incorrect call to qrcode module
Issue -
State: closed - Opened by fredcy almost 4 years ago
- 15 comments
Labels: bug
#170 - Building client with rollup and typescript results in incorrect call to qrcode module
Issue -
State: closed - Opened by fredcy almost 4 years ago
- 15 comments
Labels: bug
#170 - Building client with rollup and typescript results in incorrect call to qrcode module
Issue -
State: closed - Opened by fredcy almost 4 years ago
- 15 comments
Labels: bug
#170 - Building client with rollup and typescript results in incorrect call to qrcode module
Issue -
State: closed - Opened by fredcy almost 4 years ago
- 15 comments
Labels: bug
#170 - Building client with rollup and typescript results in incorrect call to qrcode module
Issue -
State: open - Opened by fredcy almost 4 years ago
- 14 comments
Labels: bug
#154 - Long contract call errors are too big for the default alert
Issue -
State: closed - Opened by AndreasGassmann almost 4 years ago
Labels: bug
#154 - Long contract call errors are too big for the default alert
Issue -
State: closed - Opened by AndreasGassmann almost 4 years ago
Labels: bug
#154 - Long contract call errors are too big for the default alert
Issue -
State: closed - Opened by AndreasGassmann almost 4 years ago
Labels: bug
#154 - Long contract call errors are too big for the default alert
Issue -
State: closed - Opened by AndreasGassmann almost 4 years ago
Labels: bug
#154 - Long contract call errors are too big for the default alert
Issue -
State: closed - Opened by AndreasGassmann almost 4 years ago
Labels: bug
#154 - Long contract call errors are too big for the default alert
Issue -
State: closed - Opened by AndreasGassmann almost 4 years ago
Labels: bug
#154 - Long contract call errors are too big for the default alert
Issue -
State: closed - Opened by AndreasGassmann almost 4 years ago
Labels: bug
#138 - Investigate "build issues"
Issue -
State: closed - Opened by AndreasGassmann almost 4 years ago
- 27 comments
Labels: bug
#138 - Investigate "build issues"
Issue -
State: closed - Opened by AndreasGassmann almost 4 years ago
- 27 comments
Labels: bug
#138 - Investigate "build issues"
Issue -
State: closed - Opened by AndreasGassmann almost 4 years ago
- 27 comments
Labels: bug
#131 - Introduce new error types
Issue -
State: closed - Opened by AndreasGassmann almost 4 years ago
- 4 comments
Labels: enhancement, future consideration
#131 - Introduce new error types
Issue -
State: closed - Opened by AndreasGassmann almost 4 years ago
- 4 comments
Labels: enhancement, future consideration
#114 - Replace "string" enums with numbers
Issue -
State: closed - Opened by AndreasGassmann almost 4 years ago
Labels: enhancement
#113 - Requests are not persisted
Issue -
State: closed - Opened by AndreasGassmann almost 4 years ago
Labels: enhancement, future consideration
#113 - Requests are not persisted
Issue -
State: closed - Opened by AndreasGassmann almost 4 years ago
Labels: enhancement, future consideration
#112 - Handling multiple DAppClient instances
Issue -
State: open - Opened by AndreasGassmann almost 4 years ago
- 16 comments
Labels: bug