RPC calls with wrong argument signature get dropped silently?

[GoogleCodeExporter]

Calling contactsGetCount() via RPC works as expected:

command string:'{"id": 1, "method": "contactsGetCount", "params": []}'
Parsing response: '{"error":null,"id":1,"result":3350}
'

But if I add an extraneous argument, it just hangs, and I never get a response 
back from SL4A:

command string:'{"id": 1, "method": "contactsGetCount", "params": [7]}'

(Likewise if I call it with a string argument instead of an integer)

Original issue reported on code.google.com by credenti...@gmail.com on 4 Sep 2010 at 3:19

[GoogleCodeExporter]

I can't reproduce this with Python. Could you please post a script that causes 
this issue?

Original comment by damonkoh...@gmail.com on 9 Sep 2010 at 9:30

[GoogleCodeExporter]

Closing because this is quite stale.

Original comment by damonkoh...@gmail.com on 11 Nov 2010 at 10:07

• Changed state: WontFix