Supun Setunga

So what is failing is the core-contracts migration. Seems the expected core/system contracts cannot be found in the emulator state. Did the contract addresses change at some point in the...

Updated the guide with these points

Looking into it, could be a bug in the migration. Think I know what's happening

@nvdtf Does the contracts section in `flow.json` points to the 'updated' code of `ExampleNFT`? ```json { "contracts": { "ExampleNFT": "updated_ExampleNFT.cdc" }, } ```

So there were two issues: - CLI needed to replace the string import addresses with the proper addresses: Added with https://github.com/onflow/flow-cli/pull/1458 - Contract update validator was looking only at the...

@nvdtf A new CLI release with the fix is now available: https://github.com/onflow/flow-cli/releases/tag/v1.15.0-cadence-v1.0.0-preview.12 Can you please try with the new release and see if that works fine?

Thanks Josh for having a look! > But I guess since we are using it for migrations, then we do need to revert those field additions and changes. We are...

Just cross-posting from the offline thread: So yeah, like Bastian has mentioned above, at the moment, the draft PR has this function `func MigrateCadence1(...)` which takes-in a snapshot file as...

> a fork testnet to the emulator Not really sure what that is / what you meant there 🤔 This particular command should work as long as the snapshot was...

Added in https://github.com/onflow/flow-cli/pull/1426