Greg

What would the warning be? Something like "it's advised you use already deployed contract ... read more about it here"

That would be nice, I agree 100%.

I'm not a fan of lists of contracts, I feel that should be ideally decentralised and saved in such registries, so we don't special treat any contracts and control that...

> Should we replace the contract reference in state with alias ? This is a good idea yeah. > As we are not exposing direct access to state, should I...

> Because I want to prompt the user ( if they want to deploy or replace with alias ), so best option I guess: > > * to do the...

@bluesign we currently don't yet support saving to multiple files as per https://github.com/onflow/flow-cli/blob/7401e49afd2d7b89e15dc8f42c75fcb279f4e60f/pkg/flowkit/state.go#L79 There's a plan to make this work in the future once we find some time.

I agree. How urgent is this? Should we just do another call or wait for AN?

@turbolent I can't seem to reproduce that flakiness locally. I've created a PR I think might help fix the test issue, but I also haven't detected that during the CI,...

> @sideninja Thank you for investigating. 🙏 I'll re-run the job and see if it shows up again Now it's something else?

> Can we try merging the PR I made in? I think it could be related to the fact I'm returning nils. https://github.com/onflow/cadence/pull/1890