This repository has been archived by the owner on Oct 4, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 94
delete returns SignerDoesNotExist, but transaction hash on explorer shows success #1012
Labels
bug
Something isn't working
Comments
@chefsale FYI |
Same here, but using just Full dump of the tx:
When broadcasting the above, I get the following error:
But in fact the transaction was executed successfully: https://explorer.mainnet.near.org/transactions/2so1WEW8AX8xdKSPVzX7wwXYKHAbNxGp67sWwjReEMDM |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
CLI returned an error (SignerDoesNotExist), and the explorer shows that the transaction succeeded.
When trying to create a new account with the same name, creation succeeds meaning the account was actually deleted.
https://explorer.testnet.near.org/transactions/EXuXxPT2JDVLaXc91jeFfdFYU9XM4gF3oAE7ufg7rRCL
https://explorer.testnet.near.org/transactions/AReUBYzad8rHSFoJDLpeVWzmCzkN4SiAaxGJimRbepGe
To Reproduce
Happend twice in many
near delete
scenarios, not sure how reproducible it is.It was called in a bash script which first funded the account:
Expected behavior
CLI should report success.
Screenshots
Desktop (please complete the following information):
Additional context
near_cli_error.txt
near --version
returns3.3.1
The text was updated successfully, but these errors were encountered: