Resource account issues (Move abort in 0x1::resource_account: 0x60001)

[davd-ops]

Discord user ID

davidbailey.eth

Describe your question in detail.

Hello, I have this code. Im having problems with publishing it on testnet.

When I run aptos move publish, Im getting Simulation failed with status: Move abort in 0x1::resource_account: 0x60001" error.

From that, I understand that the resource account was not found or that I used the wrong address in this line of code let signer_cap = resource_account::retrieve_resource_account_cap(resource_signer, @source_addr);.

Therefore I tried to follow this in order to generate the address first using create-resource-account-and-publish-packagelike this aptos move create-resource-account-and-publish-package --address-name aptos_institute --seed test (aptos institute here is an address I got when I ran the aptos move compile). But I meet another error which is saying "Error": "Unexpected error: Unable to resolve packages for package 'aptos_institute': Unable to resolve named address 'aptos_institute' in package 'aptos_institute' when resolving dependencies: Attempted to assign a different value '0x50a1c95f48059ee74cdd2dcc0b0eb60c0547ae37fef5b7231feb014a0c36baa1' to an a already-assigned named address '0x357017d43fab9fb7f46f097c69dc27cb1472ecddb28090f1652dbb1b3f604527'"

Okay, so I try to use that new address I just got as the the address when I run create-resource-account-and-publish-package. That asks me if I really want to publish this package the resource account's address 0x357017d43fab9fb7f46f097c69dc27cb1472ecddb28090f1652dbb1b3f604527. I say yes. And get another error - "Simulation failed with status: MODULE_ADDRESS_DOES_NOT_MATCH_SENDER".

I don't understand how am I suppose to publish with resource accounts at all. Could someone help me with what address to use? Or if I am doing something else wrong, point me to the mistake?

Thank you

What error, if any, are you getting?

No response

What have you tried or looked at? Or how can we reproduce the error?

No response

Which operating system are you using?

macOS

Which SDK or tool are you using? (if any)

Aptos CLI

Describe your environment or tooling in detail

No response

[kshitijc1506]

I suspect the issue is coming from your Move.toml, you can use this e2e example for reference.

[davd-ops]

I am thinking that when I run the create RA and publish command, it tries to do both things at the same time, and since the RA is used within my module, it fails? Is there a way to only deploy the resource account and publish after? Not sure if that makes sense but it's the reason I can think of

[davd-ops]

This si what im getting when I changed all addresses in Move.toml to be 0x357017d43fab9fb7f46f097c69dc27cb1472ecddb28090f1652dbb1b3f604527

[davd-ops]

Okay I got some progress, I changed the init_module to not run on start but rather be a function that is called after like this
public entry fun public_init_module(resource_signer: &signer, parent_address: address) { let signer_cap = resource_account::retrieve_resource_account_cap(resource_signer, parent_address);

And I was able to execute the publish in this TX

So I think resource account should now be available? I am not sure if the module was also deployed or not I don't see it anywhere

If I now revert the changes to the init_module function and try to publish it using normal publish command, I am now getting a new error "Error": "Simulation failed with status: Move abort in 0x1::resource_account: 0x10002"

[kshitijc1506]

@davd-ops I cloned, so basically:

1. Remove source_addr from your Move.toml entirely (this is your admin_addr, AKA the account that creates the resource account) -- unless you want them to be different but I don't think that's the case.
2. Make the admin_addr the same as the account address in your config.yaml (I think this is already the case)
3. Change the named address for aptos_institute to a placeholder - the CLI needs this since @aptos_institute represents the address of the resource account after publishing.

    [addresses]
    admin_addr = "0x88b2d8344be13ca52da70764f7cb86c14bbae26e63834a65c407c182fa96d4f4"
    aptos_institute="_"

In your init_module, you need to change your retrieve_resource_account_cap to this:

let signer_cap = resource_account::retrieve_resource_account_cap(resource_signer, @admin_addr);

[kshitijc1506]

This solves the resource account issue, but, there are other runtime errors popping up in init_module. I suggest writing a few tests to utilize the stack trace and find out exactly where the error is coming from.

[kshitijc1506]

Also, I recommend you use objects for deployment and contract state storage, it's a lot easier to deal with :)