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
I agree Anchor should handle this internally. In the meantime, people can use watchso, a hot-reloading tool, that also updates the program id in the case of mismatch between the declared one and the created public key in target/deploy folder.
I agree Anchor should handle this internally. In the meantime, people can use watchso, a hot-reloading tool, that also updates the program id in the case of mismatch between the declared one and the created public key in target/deploy folder.
My tool, create-solana-starter, also handles this, but only covers Anchor so far. I'll take a look at yours and see if it makes sense to integrate it.
How can we possibly make this process smoother or go away completely?
There's two spots that can drive a dev crazy whenever a fresh build is done, or if you're developing locally and do a
cargo clean
:Anchor.toml
lib.rs
:declare_id
Is there any way we can eliminate some of the redundancy of the process of updating your program's ID?
For context, I know the process most devs typically fall into is as follows:
cargo clean
oranchor build
for the first timeanchor deploy
Incorrect program ID
errordeclare_id
andAnchor.toml
anchor build
againThe text was updated successfully, but these errors were encountered: