Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

eosio_assert_message assertion failure #2059

Closed
dev-dantealighieri opened this issue Jan 9, 2024 · 8 comments
Closed

eosio_assert_message assertion failure #2059

dev-dantealighieri opened this issue Jan 9, 2024 · 8 comments
Labels
more-info waiting for submitter to reply with more information

Comments

@dev-dantealighieri
Copy link

when I'm trying to create an account using wharfkit/antelope library, I get the following response from the transaction broadcast.

{
  transaction_id: '41e2edec3278acba808ee6d9b761786be3862af336dc17f6732319ec893d2a01',
  processed: {
    id: '41e2edec3278acba808ee6d9b761786be3862af336dc17f6732319ec893d2a01',
    block_num: 351244143,
    block_time: '2024-01-09T15:44:49.000',
    producer_block_id: null,
    receipt: null,
    elapsed: 403,
    net_usage: 165,
    scheduled: false,
    action_traces: [ [Object], [Object] ],
    account_ram_delta: null,
    except: {
      code: 3050003,
      name: 'eosio_assert_message_exception',
      message: 'eosio_assert_message assertion failure',
      stack: [Array]
    },
    error_code: '10000000000000000000'
  }
}

I can't figure out what's the problem. I'm using an account with R1 public/private key.

I can send money transactions successfully, but account creation fails like this.

following shows how I create new account action:

contract.action(
    "newaccount",
    {
      creator: creatorUsername,
      name: newAccountName,
      owner: {
        threshold: 1,
        keys: [
          {
            key: publicKey,
            weight: 1,
          },
        ],
        accounts: [],
        waits: [],
      },
      active: {
        threshold: 1,
        keys: [
          {
            key: publicKey,
            weight: 1,
          },
        ],
        accounts: [],
        waits: [],
      },
    },
    {
      authorization: [
        {
          actor: creatorUsername,
          permission: "owner",
        },
      ],
    },
  );

and the following shows how I create buy ram action

contract.action(
    "buyrambytes",
    {
      payer: payerUsername,
      receiver: receiverUsername,
      bytes: ramBytes,
    },
    {
      authorization: [
        {
          actor: payerUsername,
          permission: "owner",
        },
      ],
    },
  );

the contract here is coming from import { Contract } from '@wharfkit/contract';

@enf-ci-bot enf-ci-bot moved this to Todo in Team Backlog Jan 9, 2024
@bhazzard bhazzard added more-info waiting for submitter to reply with more information and removed triage labels Jan 9, 2024
@bhazzard
Copy link

bhazzard commented Jan 9, 2024

Is it possible to reproduce but get the expanded output including the stack for that eosio_assert_message_exception?

This could be any error while trying to create an account:

  • invalid account name
  • not enough ram
  • etc

It's not possible to tell without the full contents of the assert message exception.

@dev-dantealighieri
Copy link
Author

I have enough ram, my account name, and destination is correct. I am trying to send some money actually, I have enough cpu and net resources, I have rented them. but still got this error, and can't figure out how to solve it.

@matthewdarwin
Copy link

Better to ask questions in telegram channels rather than here. https://t.me/antelopedevs

@heifner
Copy link
Member

heifner commented Jan 12, 2024

@dev-dantealighieri I believe your issue was resolved on telegram.

@heifner heifner closed this as completed Jan 12, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in Team Backlog Jan 12, 2024
@dev-dantealighieri
Copy link
Author

First of all, I couldn't find a resolved answer to my problem in your telegram, if i'm missing something, can you please show me?

if i switch to an account with K1 private keys, without changing any part of the transaction (only creator username and private key changes), i can create both r1 and k1 accounts(new accounts) (still sometimes i get errors but i dont mind that now, sending transaction again usually works.)

What is the problem here? how can i solve it, can i create new accounts using r1 key as creator? i appreciate your time and answers,

have a good day

@heifner heifner reopened this Jan 16, 2024
@github-project-automation github-project-automation bot moved this from Done to Todo in Team Backlog Jan 16, 2024
@heifner
Copy link
Member

heifner commented Jan 16, 2024

Sorry, someone asked a similar question on telegram, I assumed it was you.

@spoonincode
Copy link
Member

@dev-dantealighieri is this still an issue for you?

@dev-dantealighieri
Copy link
Author

no thanks, suddenly it started working, i dunno why!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
more-info waiting for submitter to reply with more information
Projects
Status: Done
Development

No branches or pull requests

6 participants