You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when I deploy using Pop CLI, the deployed contract does not show up in ui.use.ink (or PolkadotJs Apps > Contracts).
As a developer, I need a way for when I deploy a contract using Pop CLI, that it shows up on the ui.use.ink because that UI is useful for debugging and part of the development process.
ui.use.ink is an invaluable tool in the smart contract development workflow
The text was updated successfully, but these errors were encountered:
Are you experimenting the same when deploying a smart contract using cargo-contract?
This might need more research but seems more an issue of ui.use.ink that fails to show the contract.
Are you experimenting the same when deploying a smart contract using cargo-contract? This might need more research but seems more an issue of ui.use.ink that fails to show the contract.
Same. For both cases I have to go to ui.use.ink and manually add the code_hash of the deployed contract for the contract to show up in the UI.
It seems like the issue might be on the ui.use.ink side, right? If the contract is deployed correctly on-chain, there’s probably not much we can address directly from the CLI.
It seems like the issue might be on the ui.use.ink side, right? If the contract is deployed correctly on-chain, there’s probably not much we can address directly from the CLI.
Yes, and it is critical to the success of Pop CLI smart contract development workflow.
Currently when I deploy using Pop CLI, the deployed contract does not show up in ui.use.ink (or PolkadotJs Apps > Contracts).
As a developer, I need a way for when I deploy a contract using Pop CLI, that it shows up on the ui.use.ink because that UI is useful for debugging and part of the development process.
ui.use.ink is an invaluable tool in the smart contract development workflow
The text was updated successfully, but these errors were encountered: