UI + PoA: Sending tx fails

[chevdor]

The following issue occurs in builds from the latest master.
The issue occurs when using PoA in a similar way than described at https://github.com/ethcore/parity/wiki/Demo-PoA-tutorial

Once the PoA chains runs, sending tx through RPC works fine. When doing so, the parity UI shows the signer dialog and prompt the user to enter his account password, then the tx goes to the blockchain => all good.

Making a tx (simple ETH transfer) from the UI however fails. It remains stuck with the following dialog forever:

[keorn]

The UI needs a wider set of RPC apis enabled than the one in tutorial, I will add a note. Try running without --jsonrpc-apis or adding all default ones.

[tomusdrw]

UI is using Secure Signer interface which has all APIs exposed, maybe it's just not using the correct one? (iirc UI is using parity_postTransaction instead of eth_sendTransaction, could that be causing any issues?)

[chevdor]

@keorn I am already using
apis = ["web3", "eth", "net", "personal", "parity", "parity_set", "traces", "rpc", "parity_accounts"]
so I don´t think this is the issue.

[keorn]

Yep, just had a similar issue when writing the tutorial which afair was caused by this, will have a look what might be the issue this time.

[chevdor]

@keorn great tuto btw.

[keorn]

@tomusdrw When I run with rpc=trace

2017-02-01 03:40:00   TRACE rpc  Request: {"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":232}.
2017-02-01 03:40:00   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":\"0x0\",\"id\":232}").
2017-02-01 03:40:00   TRACE rpc  Request: {"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":233}.
2017-02-01 03:40:00   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":false,\"id\":233}").
2017-02-01 03:40:00   TRACE rpc  Request: {"jsonrpc":"2.0","method":"signer_requestsToConfirm","params":[],"id":234}.
2017-02-01 03:40:00   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":[],\"id\":234}").
2017-02-01 03:40:01   TRACE rpc  Request: {"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":235}.
2017-02-01 03:40:01   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":\"0x0\",\"id\":235}").
2017-02-01 03:40:01   TRACE rpc  Request: {"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":236}.
2017-02-01 03:40:01   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":false,\"id\":236}").
2017-02-01 03:40:02   TRACE rpc  Request: {"jsonrpc":"2.0","method":"signer_requestsToConfirm","params":[],"id":237}.
2017-02-01 03:40:02   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":[],\"id\":237}").
2017-02-01 03:40:02   TRACE rpc  Request: {"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":238}.
2017-02-01 03:40:02   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":\"0x0\",\"id\":238}").
2017-02-01 03:40:02   TRACE rpc  Request: {"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":239}.
2017-02-01 03:40:02   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":false,\"id\":239}").
2017-02-01 03:40:03   TRACE rpc  Request: {"jsonrpc":"2.0","method":"signer_requestsToConfirm","params":[],"id":240}.
2017-02-01 03:40:03   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":[],\"id\":240}").
2017-02-01 03:40:03   TRACE rpc  Request: {"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":241}.
2017-02-01 03:40:03   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":\"0x0\",\"id\":241}").
2017-02-01 03:40:03   TRACE rpc  Request: {"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":242}.
2017-02-01 03:40:03   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":false,\"id\":242}").
2017-02-01 03:40:04   TRACE rpc  Request: {"jsonrpc":"2.0","method":"signer_requestsToConfirm","params":[],"id":243}.
2017-02-01 03:40:04   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":[],\"id\":243}").
2017-02-01 03:40:04   TRACE rpc  Request: {"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":244}.
2017-02-01 03:40:04   TRACE rpc  Request: {"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":245}.
2017-02-01 03:40:04   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":false,\"id\":245}").
2017-02-01 03:40:04   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":\"0x0\",\"id\":244}").
2017-02-01 03:40:05   TRACE rpc  Request: {"jsonrpc":"2.0","method":"signer_requestsToConfirm","params":[],"id":246}.
2017-02-01 03:40:05   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":[],\"id\":246}").
2017-02-01 03:40:05   TRACE rpc  Request: {"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":247}.
2017-02-01 03:40:05   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":false,\"id\":247}").
2017-02-01 03:40:05   TRACE rpc  Request: {"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":248}.
2017-02-01 03:40:05   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":\"0x0\",\"id\":248}").
2017-02-01 03:40:06   TRACE rpc  Request: {"jsonrpc":"2.0","method":"signer_requestsToConfirm","params":[],"id":249}.
2017-02-01 03:40:06   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":[],\"id\":249}").
2017-02-01 03:40:06   TRACE rpc  Request: {"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":250}.
2017-02-01 03:40:06   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":false,\"id\":250}").
2017-02-01 03:40:06   TRACE rpc  Request: {"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":251}.
2017-02-01 03:40:06   DEBUG rpc  Response: Some("{\"jsonrpc\":\"2.0\",\"result\":\"0x0\",\"id\":251}").

Dont see any tx posting after clicking "SEND".

Can be replicated by running parity --chain demo-spec.json with this file. Account with balance can be created with phrase "user". This will not seal a transaction but should be able to only submit it fine (direct send RPC works fine).