During my daily round of issues while dapp soroban developement I'm currently getting one that is kind of weird because I'm not really sure what resource I'm hitting.
This tx https://horizon-futurenet.stellar.org/transactions/0bfc5a89920949eccd6a6c774bde168df714736019ba6907f5e6ba28a3b2bf3e is a simple transfer between two accounts using the native asset contract. So the response gives this error:
{
"fee_charged": 27050,
"result": {
"tx_failed": [
{
"op_inner": {
"invoke_host_function": "resource_limit_exceeded"
}
}
]
},
"ext": "v0"
}
From the tx meta I can see this diagnostic event:
"diagnostic_events": [
{
"in_successful_contract_call": false,
"event": {
"ext": "v0",
"contract_id": null,
"type_": "diagnostic",
"body": {
"v0": {
"topics": [
{
"symbol": "error"
},
{
"error": {
"budget": "exceeded_limit"
}
}
],
"data": {
"vec": [
{
"string": "operation byte-read resources exceeds amount specified"
},
{
"u64": 520
},
{
"u64": 480
}
]
}
}
}
}
}
]
So there it says what the issue is... The problem is that the tx is being build with a simulation from the js sdk so I assume the simulation (and later use of the assembleTransaction method) should take care of setting the correct specified amounts right?