listtransactions unconfirmed problem BOUNTY

[williamj2543]

I am programming with blockchain's daemon, and I found that if I did listtransactions for an address with an unconfirmed transaction, the php script would have an error, and as soon as it got confirmed, it would work finely. I am making a script to be ran every 15 or so seconds to process transactions coming into an address, and I can't have the whole script fail until every single transaction confirms.
Here is the error I get as soon as I send a transaction which is unconfirmed:

Code:

Fatal error: Uncaught exception 'Exception' with message 'Incorrect response id (request id: 1, response id: )' in /home/crypsizy/public_html/jsonRPCClient.php:152 Stack trace: #0 /home/crypsizy/public_html/bitcoind.php(22): jsonRPCClient->__call('listtransaction...', Array) #1 /home/crypsizy/public_html/bitcoind.php(22): jsonRPCClient->listtransactions('18wEYfiCauuGnag...', 10) #2 {main} thrown in /home/crypsizy/public_html/jsonRPCClient.php on line 152

0.002 BTC bounty for this (Small, buy a chocolate bar or something, its not a very complicated question).

[1715289769]

1715289769

[1715289769]

1715289769

[1715289769]

1715289769

[1715289769]

1715289769

[1715289769]

1715289769

[1715289769]

1715289769

[Envrin]

Wrap an exception around your code doing the RPC call:

Code:

try{
     $client->listtransactions();
} catch (Exception $e) { 
     echo "Didn't work -- " . $e->getMessage();
}

[williamj2543]

Wrap an exception around your code doing the RPC call:

Code:

try{
     $client->listtransactions();
} catch (Exception $e) { 
     echo "Didn't work -- " . $e->getMessage();
}

Tried that, still returned an error

Code:

Didn't work -- Incorrect response id (request id: 1, response id: )

[JCaferJr]

This is still an issue on blockchain.info


***** Request *****
{"method":"listtransactions","params":["TestLabel",100],"id":1}
***** End Of request *****

***** Server response *****
{"jsonrpc":"2.0","error":{"code":-32603,"message":null}}
***** End of server response *****

Anyone know of a work-around besides using listsinceblock?