Skip to content
This repository was archived by the owner on Nov 10, 2025. It is now read-only.
This repository was archived by the owner on Nov 10, 2025. It is now read-only.

Tx showed HALT in ApplicationLogs but has exception returned #854

@superboyiii

Description

@superboyiii

Describe the bug
0x0819175f7cd906f2eee8fbc825496acd11f0f0afcfcaec32bfbb71a7a52b6f48 on testnet have such an applicationlog below:

{
    "jsonrpc": "2.0",
    "id": 1,
    "result": {
        "txid": "0x0819175f7cd906f2eee8fbc825496acd11f0f0afcfcaec32bfbb71a7a52b6f48",
        "executions": [
            {
                "trigger": "Application",
                "vmstate": "HALT",
                "exception": "Operation is not valid due to the current state of the object.",
                "gasconsumed": "6312969",
                "notifications": []
            }
        ]
    }
}

The vmstate is HALT, but the exception is not null. This can make people confusing.

To Reproduce
Steps to reproduce the behavior:
1701312079559

Expected behavior
exception is not null even vmstate is null.

Screenshots
Showed above

Platform:

  • OS: [all]
  • Version [e.g. neo-cli 3.6.3]

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions