https://github.com/MyEtherWallet/ethereum-lists
For extension (URLs): paritytech/parity-extension#91
"We could integrate the phishing list in Signer, which is used by the UI and the Chrome Extension"

Repro:

1. Clone am-electron branch. It's the master branch with an MVP to have electron working.
2. npm start in one terminal, npm run start:electron:dev in another
3. Open electron and go to v1 wallet
4. In the electron console, look at all the SHELL received messages. These are all the API calls the dapp made.
5. Now click on the Accoutns Tab on the top. Suddenly the API calls stop. All future API calls do not get to the shell whatsoever.

I did some more digging.

• In node_modules/@parity/api I added a console.log to check. that v1 is correctly sending the api calls. Yes. Only the shell is not receiving them.
• Between 4 and 5 above, in the console, type $('webview').openDevTools() to open the console of the dapp.
• When I click on the Accounts Tab (step 5 above), I see [Violation] 'setTimeout' handler took 124ms. And from that point on, all future api calls are blocked.

Moved from: openethereum/parity-ethereum#8312

I'm running:

    Which Parity version?: v1.9.5-20180321
    Which operating system?: Linux
    How installed?: via binaries .deb
    Are you fully synchronized?: yes
    Which network are you connected to?: ethereum
    Did you try to restart the node?: yes

actual

The SMS account verification failed - I received the SMS (actually I received 2 sms) but the parity interface never let me enter them.

I have tried to run confirm from the ProofOfSMS contract without any luck as detailled in #7902 , I did put as argument 0x(sha3 of the sms code I received, with or without space between the words)

expected behaviour

I would like to confirm my phone number and receive true when running certified(my address)

Cheers!

@General-Beck proposed https://github.com/electron/update.electronjs.org, which looks quite promising.

Parity must currently be launched using the absolute PATH on Windows and OSX. Adding the binary to the global PATH would help novice users.

Moved from openethereum/parity-ethereum#7963 @chevdor

I'm running:

• Which Parity version?: Parity/v1.10.0-unstable-5b4abec2d-20180219/x86_64-macos/rustc1.24.0
• Which operating system?: Windows / MacOS / Linux
• How installed?: via installer / homebrew / binaries / from source
• Are you fully synchronized?: no / yes
• Which network are you connected to?: ethereum / ropsten / kovan / ...
• Did you try to restart the node?: no / yes

I deployed a Badge.
I registered the Badge on Kovan (id: 10)
I registered an image using GithubLink:

• Image: https://raw.githubusercontent.com/chevdor/kitoken/master/EAC/EAC_Gold.png
• Hash: 0xcb54cc9ecc2d8b1222a02d8c4cb436afdf77401f74129ccc644fee52b4c73de4
  I set the Meta 0x494d47 of id: 10 to 0xcb54cc9ecc2d8b1222a02d8c4cb436afdf77401f74129ccc644fee52b4c73de4

The tx goes thru: https://kovan.etherscan.io/tx/0x5bf40b0620e8b4834ab6874211f4763993cd1a6e42415be683275d1c3d1edfbe

The Badge icon does not show up as it seems the UI fails fetching it:
5ba4bbe……b52dcfd3d9c32805f06 Failed to load resource: the server responded with a status of 502 (Bad Gateway)

DOWNLOADED BUNDLE DOES NOT CONTAIN A VALID CONTENT.
HashMismatch { expected: 5ba4bbe28c1bba5fa27336e5f8b60593a6a9a79d9f14eb52dcfd3d9c32805f06, got: ad1c95825cfd0ffa95047675164346e73bb6eabe3db315d027b97804616dcb1c }

3 solutions, in order of preference:

1. Let the installer auto-fetch the latest version of parity

Parity would be fetched at install time, installed by the installer (so that parity command would be available in $PATH). I'm not sure how feasible this is on the 3 os.

2. Let Electron auto-fetch the latest version of parity

Parity would be fetched at first-run of the Electron app. However parity would be located in a non-standard location, so wouldn't be available via parity command.

3. Pre-bundle a specific version of parity in the installer

The easy way. However Parity UI release cycle would need to be tightly coupled to parity's release cycle.

Moved from openethereum/parity-ethereum#4123 by @cseberino
When submitting contracts and other things that require payments, Parity labels
currency as ETH even when should be ETC.

Possible to somehow add a conditional instruction in code to adjust when "--chain classic"
switch used?

Coming from openethereum/parity-ethereum#7976

This is a very minor improvement to keep the UI consistent.
In the contract tab, token contracts show up with their icon, badge don´t.
It would be nice if they would as well.

I'm running:

Which Parity version?: Parity v1.10.0-20180220 unstable
Which operating system?: Windows / MacOS / Linux
How installed?: via installer / homebrew / binaries / from source
Are you fully synchronized?: no / yes
Which network are you connected to?: ethereum / ropsten / kovan / ...
Did you try to restart the node?: no / yes

I'm running:

• Parity client version: 0.0.0
• Parity UI version: 0.0.0
• Operating system: OSX
• Installed via: source
• Fully synchronized: temporarily
• Network: kovan
• I tried to restart both Parity UI and Parity Ethereum client: yes

I run

cd ~/parity/ui/shell-0.1.1/ && npm run electron

and this happens:

 installer.nsh  686 bytes          [emitted]
  [37] ./index.electron.js 7.4 kB {0} [built]
  [41] ./util/parityInstallLocation.js 3.05 kB {0} [built]
  [45] ./util/promiseAny.js 2.07 kB {0} [built]
    + 78 hidden modules

> [email protected] build:embed /Users/quantum/parity/ui/shell-0.1.1
> cross-env EMBED=1 node webpack/embed

internal/modules/cjs/loader.js:550
    throw err;
    ^

Error: Cannot find module '..'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:548:15)
    at Function.Module._load (internal/modules/cjs/loader.js:475:25)
    at Module.require (internal/modules/cjs/loader.js:598:17)
    at require (internal/modules/cjs/helpers.js:11:18)
    at Object.<anonymous> (/Users/quantum/parity/ui/shell-0.1.1/node_modules/.bin/cross-env:4:16)
    at Module._compile (internal/modules/cjs/loader.js:654:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:665:10)
    at Module.load (internal/modules/cjs/loader.js:566:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:506:12)
    at Function.Module._load (internal/modules/cjs/loader.js:498:3)
npm ERR! code ELIFECYCLE

I expected it to launch the UI. It didn't. I uninstalled node_modules, reinstalled then ran again and this works.

Why did this happen? Will this break in the future?

(I never restarted parity cli once during this process)

A couple of thoughts:

• We want to separate company and products a bit, and should consider finding a good name for what we call "Parity UI" now.
  • "UI" is an overly technical term, maybe we can be more creative?
  • I have no strong opinion on keeping or removing "Parity" from the name, however, this will sooner or later happen for the Ethereum and Bitcoin client too.
• If this is the umbrella repository for the "Parity UI," we should rename it to something else then "shell."

Let's brainstorm a bit.

Since an AppImage is supposed to be self-contained (i.e., have no dependencies other than the target system/distribution), Parity should be bundled inside the AppImage and should be launched before the UI is launched. So that this is never shown:

AppImage is meant to do away with the need to install anything. One app = one file, just download and run.

From openethereum/parity-ethereum#6783 by @MicahZoltu

The recent Simolean airdrop to every Ethereum account has made it so all of my accounts/contractsin Parity now show me as having 10,000 Simoleans. This is quite annoying since they are worthless and this is really just an advertising scheme. As a user, I would like the ability to click on a token in the UI and have it blacklisted so it no longer shows up for me.

I'm worried that the whole "automatically list tokens" thing is going to become more and more problematic as advertisers realize that for a couple of dollars they can make their random worthless token show up on everyone's account in Parity (and likely other wallet UIs). I'm not sure what the best long-term solution for this is since I think we are all generally against censorship, but at the same time I think we need a way to mitigate this sort of low-cost spam.

Please consider posting a docker image

Moved from openethereum/parity-ethereum#7825 by @schmidsi

• Which Parity version?: v1.9.1-beta
• Which operating system?: MacOS
• How installed?: via installer
• Are you fully synchronized?: yes
• Which network are you connected to?: kovan
• Did you try to restart the node?: yes

Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue.

If I create a WebExtension specs compliant manifest.json file like:

 {
   "id": "melon",
   "short_name": "Melon",
   "name": "Melon Frontend",
   "description": "The Melon Frontend",
   "version": "0.6.0",
   "author": "Melonport AG",
   "icons": [
    {
      "src": "melon-icon.jpg",
      "sizes": "128x128",
      "type": "image/jpg"
    }
   ],
   "start_url": "./index.html",
   "display": "standalone",
   "theme_color": "#000000",
   "background_color": "#FFFDF3"
 }

Parity prints an error to the console during startup:

Cannot read manifest file at: "/Users/schmidsi/Library/Application Support/io.parity.ethereum/dapps/melon/manifest.json". Error: "ErrorImpl { code: Message(\"unknown field `icons`, expected one of `id`, `name`, `description`, `version`, `author`, `iconUrl`, `localUrl`\"), line: 8, column: 9 }"

It would be nice if Parity could read official manifest.json files and furthermore use the specified fields instead of the own proprietary implementation for fields like: iconUrl, localUrl

Your readme says:

Change to the js directory inside parity/

There is no js directory, there's a json directory. https://github.com/paritytech/parity

Seems like the current package has a dependency of name of x11 and/or gnome applications. Any details on why?

I'm running:

• Parity client version: Parity/v1.10.0-beta-0a9d41e-20180320/x86_64-macos/rustc1.24.1
• Parity UI version: 0.1.0.237
• Operating system: MacOS
• Installed via: binaries
• Fully synchronized: yes
• Network: kovan
• I tried to restart both Parity UI and Parity Ethereum client: yes

When attempting to use the Contracts / Develop option in the electrum client, the following error is presented:

EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self' ".

Originate from openethereum/parity-ethereum#7646 from @HuangFJ

I'm running:

• Which Parity version?: 1.7.11
• Which operating system?: MacOS
• How installed?: via homebrew
• Are you fully synchronized?: no
• Which network are you connected to?: ethereum classic
• Did you try to restart the node?: yes

Before filing a new issue, please provide the following information.

I'm running:

• Parity client version: 1.11
• Parity UI version: 0.2.0
• Operating system: Windows (UI) / Linux (Node)
• Installed via: installer / curl
• Fully synchronized: yes
• Network: ethereum
• I tried to restart both Parity UI and Parity Ethereum client: yes

UI crashes.

Log:

2018-05-10 11:53:07  Starting Parity/v1.11.0-beta-62ccdd7ad-20180508/x86_64-windows-msvc/rustc1.25.0
2018-05-10 11:53:07  Keys path C:\Users\username\AppData\Roaming\Parity\Ethereum\keys\Foundation
2018-05-10 11:53:07  DB path C:\Users\username\AppData\Local\Parity\Ethereum\chains\ethereum\db\906a34e69aec8c0d
2018-05-10 11:53:07  Path to dapps C:\Users\username\AppData\Roaming\Parity\Ethereum\dapps
2018-05-10 11:53:07  State DB configuration: fast
2018-05-10 11:53:07  Operating mode: active
2018-05-10 11:53:07  Configured for Foundation using Ethash engine
2018-05-10 11:53:07  Unable to listen on 127.0.0.1:8546
WebSockets address 127.0.0.1:8546 is already in use, make sure that another instance of an Ethereum client is not running or change the address using the --ws-port and --ws-interface options.
2018-05-10 11:53:07  Public node URL: enode://195dcf8a4d83e7427e0f79a8711f909d8bd2a07c8f2b4bef9c620a8d99380908184989cf73bb7b9b882638cda8b932b311a80a38a5ce6ca521ae9fcece025385@127.0.0.1:30303
2018-05-10 11:53:07  Failed to auto-update latest ETH price: Fetch(Hyper(Io(Custom { kind: Other, error: Os { code: 10093, kind: Other, message: "Either the application has not called WSAStartup, or WSAStartup failed." } })))`

Tunnel line: `ssh -L 8180:localhost:8180 -L 8545:localhost:8545 -L 8546:localhost:8546 mynode

I ran sudo snap install parity-ui --beta, and got snap "parity-ui" is already installed, see "snap refresh --help".

However, when I run parity-ui I get command not found: parity-ui.

Originally in openethereum/parity-ethereum#8422 by @chevdor

I'm running:

• Which Parity version?: Parity/v1.11.0-unstable-0a170efaa-20180411/x86_64-macos/rustc1.25.0
• Which operating system?: Windows / MacOS / Linux
• How installed?: via installer / homebrew / binaries / from source
• Are you fully synchronized?: no / yes
• Which network are you connected to?: ethereum / ropsten / kovan / ...
• Did you try to restart the node?: no / yes

For whatever reason, my node is now alternating between having 1 and 2 peers. This is not great but that´s what it is now.

The way the UI is built makes very annoying as the red banner saying "You are connected to only one peer. Your node might not be reliable. Check your network connection." is shifting the UI down and up and down and up. This makes parity totally unusable as you will likely click on the wrong UI element.

A simple workaround would be to show the banner as overlay and stop shifting the UI down.

Release: Parity UI v0.1.1-beta
Do not have .dmg installation file

Before filing a new issue, please provide the following information.

I'm running:

• Parity client version: Parity v1.10.0-20180320 beta
• Parity UI version: 0.1.0
• Operating system: MacOS High Sierra 10.13.4
• Installed via: installer
• Fully synchronized: yes
• Network: ethereum
• I tried to restart both Parity UI and Parity Ethereum client: Yes

Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue.

I created a transaction last Thursday or so to send some ETH between my own accounts. A transaction hash was created and the transaction window appeared. However, it was never broadcast to the network and has received zero confirmation as a result. This transaction window appears each time I restart the Parity UI. It also appears when I run the old web UI. I can click on it and it will disappear but it does not show up in the Signer in either UI, either before or after clicking it. My node has been synced for days but the transaction never broadcasts and persists in limbo across client and OS restarts.

I need to send funds now but I am not sure I should until I can resolve this issue.

Is it possible to cancel a transaction after I've approved it? How can I get this transaction to broadcast and get confirmed by the network?

Some ideas for removing deprecated stuff in the codebase:

• After openethereum/parity-ethereum#8539 gets merged, we won't be able to use Parity UI in the browser anymore. We can remove all <iframes>, if (isElectron())...
• Remove all Rust files
• Use yarn.lock instead of package-lock.json?

From openethereum/parity-ethereum#2285 (comment) by @jacogr

After #3382.

We want to prevent random untrusted dapps from accessing a user's list of accounts. Dapps should each see only the list of accounts that the user desires them to see, rather than all of them as at present. Signer snippet UI should support editing this list, possible while using the Dapp.

• Signer should allow user to configure which dapps can see which accounts;
• RPC should only report accounts that the dapp is allowed to see.

(Split from https://github.com/ethcore/parity/issues/2118)

The documentation on Parity UI seems scarce....
I downloaded the deb pkg and installed it..... But I am unsure how to launch it.

Could use a little guidance on this...

From openethereum/parity-ethereum#6784 by ncsolar

• Parity version: Parity//v1.8.0-beta-9882902-20171015/x86_64-macos/rustc1.20.0
• Operating system: MacOS
• And installed: binaries

Expected: After connecting the Trezor and entering the correct pin and being ask to enter a passphrase on the trezor a new field to enter that info

Actual: After entering the correct pin, Parity shows that the pin is incorrect but the trezor ask to enter a passphrase, there is no new field to enter that info

I'm running:
Parity UI v1.10.1-20180413 beta
MacOS (High Sierra v10.13.4)
Installed via installer
Not synchronized - this is the problem

Which network are you connected to?: Not sure how to check, but the purpose is to work with >ethereum.
Did you try to restart the node?: I've quit and restarted the app several times to no avail; the sync >keeps freezing at a random point of progress.

I installed Parity UI via the installer .DMG; left it syncing on my iMac (High Sierra v10.13.4) returned to find it at 66.85% sync. Left again, came back four hours later - still at 66.85%. There appears to be only one log, made at 12:25:05 2018-04-22 (four hours ago, ish), which says: "Syncing snapshot 843/1261 #868400 26/50 peers 994 KiB chain 66 MiB db 0 bytes queue 10 KiB sync RPC: 1 conn, 1 req/s, 50 µs"

Activity monitor says parity's been running for a while and received a good deal of information, plus I've heard the fan running pretty hard all this time, so SOMETHING seems to be working... just not sure what.

Followup Q: will I still be able to interface with Parity UI from the Terminal? I'm trying to get started with Vyper, and it's been incredibly difficult/information-sparse, to say the least. Any pointers on how to get Vyper up and running in the simplest way possible would be amazing. My background is in biology and pythonic data science, not network/node-based stuff like this.

I'm running:

• Parity client version: 1.10.2-beta
• Parity UI version: v0.1.1-beta
• Operating system: Ubuntu 18.04
• Installed via: x64 deb package from github releases page
• Fully synchronized: yes
• Network: ethereum
• I tried to restart both Parity UI and Parity Ethereum client: yes

actual:
White screen. no useful information except sync status
expected behavior
Old good interface with wallets.
steps to reproduce
new ubuntu 18.04 x64. timezone: utc+2
Install http://d1h4xl4cr1h0mo.cloudfront.net/v1.10.2/x86_64-unknown-linux-gnu/parity_1.10.2_ubuntu_amd64.deb
https://github.com/parity-js/shell/releases/download/v0.1.1/parity-ui_0.1.1_amd64.deb
run parity --light
run parity-ui in over terminal

OS: MacOS Sierra, updated to the latest

I uninstalled 1.8.5 beta today and installed 1.10.0 node and corresponding UI. I created a transaction to send from one of my accounts to another using the new UI. I was prompted for my password, I entered it and a transaction hash was displayed. However, the account balances were not updating to reflect the transaction. My node was synced prior to creating the transaction and remained synced during the transaction process. I waited several minutes. The transaction was not reflected in the UI or on-chain. I repeated the transaction twice more since I was only sending to myself. Still no sign of the transaction. I then quit the Parity node and UI processes on the Mac and started Parity with the --force-ui flag to try the old browser UI. I granted the UI access to the accounts when prompted. The balances were still not reflecting the transaction. I created the same transaction again using the web UI, entered my password when prompted and the transaction was signed and broadcast successfully. Immediately following that, several signing requests appears in the web UI, some requesting to transfer the amount equaling that which was just sent successfully and some requesting to send 0.00 value between my accounts. It took several additional attempts at cancelling these requests before they would disappear from the signing queue.

I have not created any subsequent transactions so the above is the extent of my experience thus far.

I'm running:

• Parity client version: 1.9.6
• Parity UI version: 0.1.0
• Operating system: MacOS
• Installed via: installer
• Fully synchronized: no
• Network: ethereum
• I tried to restart both Parity UI and Parity Ethereum client: yes

My parity node runs in a docker on a remote machine on the network. It seems that Parity UI only attempts to connect to parity node if it runs locally. Could/will you provide an option to specify remote RPC node? Please :)

Currently I use Myst UI with Parity node where Myst has --rpc http://x.x.x.x:8545 option at launch

From todr:

A suggestion for permissions - each permission should have a i icon, explaining what are the consequences:
Permission for signerRequests = allows to confirm transactions given the password to the account
Permission for accounts = allows to read your account details (addresss, name, description)

I added the JSON file, account name, password hint and password and clicked import, then got the error: "[-32023] Could not create account.".

Parity-ui in CLI doesn't have any --help or command line documentation. No information is available about --ws-port or --ws-interface (see #46)

Moved from openethereum/parity-ethereum#8472 by @mgbvox

I'm running:
Parity UI v1.10.1-20180413 beta
MacOS (High Sierra v10.13.4)
Installed via installer

Which network are you connected to?: Not sure how to check, but the purpose is to work with. >ethereum.
Did you try to restart the node?: Yes.

When attempting to run the syncing check describes in the FAQs on the Parity UI Web3 Console, I got the following errors:

I would assume this means I haven't installed web3 - but how can I be sure? I can't seem to find a list of prerequisite programs to have installed if you're trying to set up Parity as your default method of interacting with Ethereum (I do not run an ethereum node on my computer, as I do not have the space to do so - it's Parity or nothing).

I'm coming at this from a very basic level, so please describe this simply.

I'm running:

• Which Parity version?: v1.9.7-20180423 stable
• Which operating system?: Linux
• How installed?: docker-compose
• Are you fully synchronized?: yes
• Which network are you connected to?: ethereum
• Did you try to restart the node?: yes

Here is sample code contract which just trying to call pure function on another contract:

pragma solidity ^0.4.23;

contract Season {
    address[] public requests;

    constructor() public {
        requests.push(new Request());
    }

    function getRequestsByFilter() public view returns(bool) {
        Request r = Request(requests[0]);
        bool ret = r.isMatch();
        return ret;
    }
}

contract Request {  
    function isMatch() public pure returns(bool) {
        return true;
    }    
}

Contract ABI:

[{"constant":true,"inputs":[],"name":"getRequestsByFilter","outputs":[{"name":"","type":"bool"}],"payable":false,"stateMutability":"view","type":"function"},{"constant":true,"inputs":[{"name":"","type":"uint256"}],"name":"requests","outputs":[{"name":"","type":"address"}],"payable":false,"stateMutability":"view","type":"function"},{"inputs":[],"payable":false,"stateMutability":"nonpayable","type":"constructor"}]

Contract Bin:

608060405234801561001057600080fd5b50600061001b61006f565b604051809103906000f080158015610037573d6000803e3d6000fd5b508154600181018355600092835260209092209091018054600160a060020a031916600160a060020a0390921691909117905561007e565b60405160b88061028083390190565b6101f38061008d6000396000f30060806040526004361061004b5763ffffffff7c01000000000000000000000000000000000000000000000000000000006000350416633bef595f811461005057806381d12c5814610079575b600080fd5b34801561005c57600080fd5b506100656100ba565b604080519115158252519081900360200190f35b34801561008557600080fd5b50610091600435610192565b6040805173ffffffffffffffffffffffffffffffffffffffff9092168252519081900360200190f35b60008060008060008154811015156100ce57fe5b9060005260206000200160009054906101000a900473ffffffffffffffffffffffffffffffffffffffff1691508173ffffffffffffffffffffffffffffffffffffffff1663904e2b936040518163ffffffff167c0100000000000000000000000000000000000000000000000000000000028152600401602060405180830381600087803b15801561015f57600080fd5b505af1158015610173573d6000803e3d6000fd5b505050506040513d602081101561018957600080fd5b50519392505050565b60008054829081106101a057fe5b60009182526020909120015473ffffffffffffffffffffffffffffffffffffffff169050815600a165627a7a72305820318b7facb613d242bed833cc4ace83ea4acd95062a7639ed27f4658d82c3947600296080604052348015600f57600080fd5b50609a8061001e6000396000f300608060405260043610603e5763ffffffff7c0100000000000000000000000000000000000000000000000000000000600035041663904e2b9381146043575b600080fd5b348015604e57600080fd5b5060556069565b604080519115158252519081900360200190f35b6001905600a165627a7a72305820731ac26809b20b529d23798a127c0ef6da8e5f6e6aced6917381b51fe430f8ea0029

Expected behaviour:
getRequestsByFilter returns true.
requests(0) returns some address

Actual behaviour:
Contract is completely broken, all properties are default:

However, if I call it via JSON RPC I get correct values:

[Fact]
public async Task Should_CreateRequestSuccessfully()
{
    const string abi = "[{\"constant\":true,\"inputs\":[],\"name\":\"getRequestsByFilter\",\"outputs\":[{\"name\":\"\",\"type\":\"bool\"}],\"payable\":false,\"stateMutability\":\"view\",\"type\":\"function\"},{\"constant\":true,\"inputs\":[{\"name\":\"\",\"type\":\"uint256\"}],\"name\":\"requests\",\"outputs\":[{\"name\":\"\",\"type\":\"address\"}],\"payable\":false,\"stateMutability\":\"view\",\"type\":\"function\"},{\"inputs\":[],\"payable\":false,\"stateMutability\":\"nonpayable\",\"type\":\"constructor\"}]";
    const string bin = "608060405234801561001057600080fd5b50600061001b61006f565b604051809103906000f080158015610037573d6000803e3d6000fd5b508154600181018355600092835260209092209091018054600160a060020a031916600160a060020a0390921691909117905561007e565b60405160b88061028083390190565b6101f38061008d6000396000f30060806040526004361061004b5763ffffffff7c01000000000000000000000000000000000000000000000000000000006000350416633bef595f811461005057806381d12c5814610079575b600080fd5b34801561005c57600080fd5b506100656100ba565b604080519115158252519081900360200190f35b34801561008557600080fd5b50610091600435610192565b6040805173ffffffffffffffffffffffffffffffffffffffff9092168252519081900360200190f35b60008060008060008154811015156100ce57fe5b9060005260206000200160009054906101000a900473ffffffffffffffffffffffffffffffffffffffff1691508173ffffffffffffffffffffffffffffffffffffffff1663904e2b936040518163ffffffff167c0100000000000000000000000000000000000000000000000000000000028152600401602060405180830381600087803b15801561015f57600080fd5b505af1158015610173573d6000803e3d6000fd5b505050506040513d602081101561018957600080fd5b50519392505050565b60008054829081106101a057fe5b60009182526020909120015473ffffffffffffffffffffffffffffffffffffffff169050815600a165627a7a72305820318b7facb613d242bed833cc4ace83ea4acd95062a7639ed27f4658d82c3947600296080604052348015600f57600080fd5b50609a8061001e6000396000f300608060405260043610603e5763ffffffff7c0100000000000000000000000000000000000000000000000000000000600035041663904e2b9381146043575b600080fd5b348015604e57600080fd5b5060556069565b604080519115158252519081900360200190f35b6001905600a165627a7a72305820731ac26809b20b529d23798a127c0ef6da8e5f6e6aced6917381b51fe430f8ea0029";


    var web3 = new Web3(new ManagedAccount(EthereumSettings.AccountAddress, EthereumSettings.AccountPassword),
                        EthereumSettings.ParityConnectionString);
    var receipt = await web3.Eth.DeployContract.SendRequestAndWaitForReceiptAsync(abi, bin, web3.TransactionManager.Account.Address,
                                                                                  new HexBigInteger(4600000));
    var contract = web3.Eth.GetContract(abi, receipt.ContractAddress);
    var requestsCallResult = await contract.GetFunction("requests").CallAsync<string>(functionInput: 0);
    var getRequestsByFilterCallResult = await contract.GetFunction("getRequestsByFilter").CallAsync<bool>();

    Assert.NotNull(requestsCallResult);
    Assert.True(getRequestsByFilterCallResult);
}

How I check if it's broken

I set breakpoint on asserts. Then I watch receipt.ContractAddress and then add it via parity UI Watch button.

Issue is related to openethereum/parity-ethereum#8503

OS: MacOS Sierra (updated to the latest)
Parity: 1.10.0
Parity UI: 1.10.0
Node Health: SYNC

When I click on etherscan.io hyperlinks in my wallet transaction lists in the new UI no browser is opened and thus no page is loaded to view the transaction details on the blockchain. If I run Parity using --force-ui and click the hyperlinks using the browser-based UI the etherscan.io links are loaded in the browser.

From issue openethereum/parity-ethereum#7820 @Flasky

I'm running:

• Which Parity version?: 1.9.2
• Which operating system?: Windows 10
• How installed?: via installer
• Are you fully synchronized?: yes
• Which network are you connected to?: ethereum
• Did you try to restart the node?: yes

Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue.

1)Parity client detects a connected Nano Ledger S, but is unable to confirm request throwing error "32602 invalid params: invalid type: null, expected string"

No prompt on the Nano Ledger S itself either.

2)Parity does not show Accounts list if Nano Ledger S is connected before starting the Parity Client.

I'm running:

• Parity client version: 1.10.1
• Parity UI version: v0.1.1 beta
• Operating system: Windows
• Installed via: installer
• Fully synchronized: yes
• Network: ethereum
• I tried to restart both Parity UI and Parity Ethereum client: no / yes

Not really an issue rather.

You've removed browser UI access in 1.10.1, but that means the node can't be accessed over LAN via Remote Access, which means you can't run the node on one computer and the client on another which reduces security.

I store none of my keys on the node computer, now I have to compromise by exposing them to the node.

Ref: openethereum/parity-ethereum#6654

This is not an issue with a specific version but a suggestion of a new feature.

Currently, one may watch or deploy a contract and then use the Edit button to add tags.
The suggestion consists in offering a way to define tags (optionally) from the UI used to watch / deploy and save a step.

Moved from openethereum/parity-ethereum#7257 by @epheph

I'm running:

• Which Parity version?: 1.8.3 and 1.9 nightly
• Which operating system?: Linux
• How installed?: via docker
• Are you fully synchronized?: yes
• Did you try to restart the node?: n/a

When executing a transaction-creating function on a custom contract with a uint256 field, the interface does something unexpected when backspacing when in "eth" mode (rightmost slider flipped right, to blue). Whenever you are deleting the first number after the period, it deletes the number AND the decimal itself. For example, type:

1.3
then try to erase the 3 to replace with a 4. When this issue is encountered, you end up with "14" instead of 1.3.

This seems like a small issue, but I have run into several cases where I was at risk of transferring 10x the value i was expecting

When recovering an account :

• If you enter all information but do not upload the JSON then click import, the error message isn't clear for users:

-32023: Could not create account.

• If you enter all information but have a wrong password, upload the JSON and then click import, the error message isn't clear for users:

-32023: Could not create account.

Originally posted by chevdor in openethereum/parity-ethereum#8174

I'm running:

• Which Parity version?: Parity/v1.11.0-unstable-9e294d577-20180320/x86_64-macos/rustc1.24.1
• Which operating system?: Windows / MacOS / Linux
• How installed?: via installer / homebrew / binaries / from source
• Are you fully synchronized?: no / yes
• Which network are you connected to?: ethereum / ropsten / kovan / ...
• Did you try to restart the node?: no / yes

I am deploying a contract. It requires ~588k gas. Parity estimates around 700k gas.
I am deploying the contract with the same arguments and those do NOT throw.

If I don´t use the advanced sending options for sending the tx, the contract deploys all fine:
https://kovan.etherscan.io/tx/0x7a2623afe89dd5389ce392edea0e16be360fbf19a6620b3a64712291085f4a76

Now in advanced sending mode, I see:

• gas: estimated 588k, will send 706446 (fine)
• price: 22000000010 (whatever :))
  The UI confirms the values:
  

And... demo effect... now it works: https://kovan.etherscan.io/tx/0x4a52daf0a93660ac325f6939d0d9e67e5b09b1baf77aa7bbe685e7c51276100c

I have done the same a few times and got those tx:

• https://kovan.etherscan.io/tx/0x7d719bfb0a7e17523fdb779ed6bf2c81f8cb23392cc80707ae165f8cf0f8d16e
• https://kovan.etherscan.io/tx/0x22fa1901d1bccabc8665c785b01f4859599cdfd127d93d2456da875f740926f2
• https://kovan.etherscan.io/tx/0x8b3679d94397cd06b0e8eabff1bbbbf71a1f1a5676995f2b62cb8c51741f2006
• https://kovan.etherscan.io/tx/0xda8d7e7cba20e5e83467497330a258a9b1144eb82ed65111fa13bf48137a8235

I don´t understand where the gas value in the tx (190088) comes from. Surely this is the reason why the tx fails as this is not enough. The question is where does this value comes from and why such low value.

It seems that the issue has been fixed by NOT using the advanced sending more once.

I just saw the same issue on mainnet:

start parity
make a tx to deploy an ERC20 for instance
directly use the advanced sending option
see if your tx go thru.

I would rather not share the mainnet tx but the amount of gas sent was ~189k

I'm running:

• Which Parity version?: v1.11.0-unstable-811d165-20180404/x86_64-linux-gnu/rustc1.25.0
• Which operating system?: Linux
• How installed?: from source
• Are you fully synchronized?: no
• Which network are you connected to?: mainnet and ropsten
• Did you try to restart the node?: yes

Launching my node with --light Parity UI shows :

Connecting to the Parity Node. If this informational message persists, please ensure that your Parity node is running and reachable on the network.

I works fine with v1.10

parity --chain foundation --light
2018-04-06 15:03:40  Starting Parity/v1.11.0-unstable-811d165-20180404/x86_64-linux-gnu/rustc1.25.0
2018-04-06 15:03:40  Keys path /home/thib/.local/share/io.parity.ethereum/keys/Foundation
2018-04-06 15:03:40  DB path /home/thib/.local/share/io.parity.ethereum/chains/ethereum/db/906a34e69aec8c0d
2018-04-06 15:03:40  Path to dapps /home/thib/.local/share/io.parity.ethereum/dapps
2018-04-06 15:03:40  Running in experimental Light Client mode.
2018-04-06 15:03:45  Syncing #5387441 0x2ab8…8e36   286 hdr/s   3778+    0 Qed  #5387441    2/50 peers   929 KiB cache 3 MiB queue  RPC:  0 conn,  0 req/s,   0 µs
2018-04-06 15:03:45  Public node URL: enode://841015562d43c8037b127ee2a89f861d39beb468fecab72ad4bf369d3db8a01a5adeee0e0422cb021acea7ffeb0516db9e1211510ad353dc353b8c52165003d3@192.168.1.56:30303
2018-04-06 15:04:15     2/50 peers   3 MiB cache 0 bytes queue  RPC:  0 conn,  0 req/s,   0 µs
2018-04-06 15:04:45     2/50 peers   3 MiB cache 0 bytes queue  RPC:  0 conn,  0 req/s,   0 µs
2018-04-06 15:05:15     4/50 peers   3 MiB cache 0 bytes queue  RPC:  0 conn,  0 req/s,   0 µs
2018-04-06 15:05:45     4/50 peers   3 MiB cache 0 bytes queue  RPC:  0 conn,  0 req/s,   0 µs
2018-04-06 15:06:15     5/50 peers   3 MiB cache 0 bytes queue  RPC:  0 conn,  0 req/s,   0 µs

Moved from openethereum/parity-ethereum#6958 by @bitxchg

I'm running:

• Parity version: v1.8.2beta
• Operating system: Linux
• And installed: via installer

When running parity in light mode, there is now way to send ERC20 tokens since they aren't being shown. The blockchain is synced_Before filing a new issue, please provide the following information._

Moved from openethereum/parity-ethereum#8398 by @nicholasfoden
Before filing a new issue, please provide the following information.

I'm running:

• Which Parity version?:
  Parity/v1.10.0-beta-0a9d41e29-20180320/x86_64-windows-msvc/rustc1.24.1
  via installer
• OS: windows
• Are you fully synchronized?: yes
• Which network are you connected to?: ethereum ...
• Did you try to restart the node?: yes

expected behavior

open parity wallet ui,
click accounts,
see accounts.

actual
open parity wallet ui,
click accounts,

check dev console and receive numerous errors

Requesting API communications token for undefined
inject.js:1 Deprecation: Dapps should only used the exposed EthereumProvider on `window.ethereum`, the use of `window.parity` and `window.web3` will be removed in future versions of this injector
(anonymous) @ inject.js:1
bundle.js:1 UI version 1.10.1
commons.js:1 js-ui: i18n in `ContextProvider` disabled
get @ commons.js:1
commons.js:1 Ledger:checkJSSupport false
commons.js:1 ServiceWorker error Error: ServiceWorker is not available in your browser.
    at commons.js:1
    at Object.<anonymous> (commons.js:1)
    at t (commons.js:1)
    at Object.<anonymous> (commons.js:1)
    at t (commons.js:1)
    at Object.<anonymous> (commons.js:1)
    at t (commons.js:1)
    at Object.<anonymous> (commons.js:1)
    at t (commons.js:1)
    at Object.2216 (bundle.js:1)
(anonymous) @ commons.js:1
commons.js:1 setupWorker TypeError: s is not a constructor
    at r (commons.js:1)
    at t.setupWorker (commons.js:1)
    at t.default (commons.js:1)
    at bundle.js:1
    at Object.2216 (bundle.js:1)
    at t (commons.js:1)
    at Object.2215 (bundle.js:1)
    at t (commons.js:1)
    at window.webpackJsonp (commons.js:1)
    at bundle.js:1
(anonymous) @ commons.js:1
bundle.js:1 registryAddress 0xe3389675d0338462dC76C6f9A3e432550c36A142
commons.js:1 [checkUpgrade] available: null version: Object consensusCapability: capable
commons.js:1 starting Signer Provider...
commons.js:1 started Signer Provider
commons.js:1 starting Status Provider...
commons.js:1 registry at 0xe3389675d0338462dC76C6f9A3e432550c36A142, code 0xa981e3ab2672e592c813da27e52d902047620f5a9e8170982fb68a2d109a4e10, version 2
commons.js:1 loadAccounts SyntaxError: Unexpected string in JSON at position 92
    at JSON.parse (<anonymous>)
    at commons.js:1
    at Array.reduce (<anonymous>)
    at r (commons.js:1)
    at <anonymous>
(anonymous) @ commons.js:1
commons.js:1 started Status Provider
commons.js:1 starting Personal Provider...
commons.js:1 [lookupAddress] dappreg: 0xD70994d7020DF8052A1124561ff548f3b88744d8
commons.js:1 [lookupAddress] signaturereg: 0x44691B39d1a75dC4E0A0346CBB15E310e6ED1E86
commons.js:1 [lookupAddress] tokenreg: 0x5F0281910Af44bFb5fC7e86A404d0304B0e042F1
commons.js:1 [lookupAddress] githubhint: 0x27c41d20014fA87291006D02Ddd81B2128039BD7
commons.js:1 [lookupAddress] badgereg: 0xF74A6e92588eE0a524b44b251E0b47d1A15824f7
commons.js:1 removeDeleted SyntaxError: Unexpected string in JSON at position 92
    at JSON.parse (<anonymous>)
    at commons.js:1
    at Array.reduce (<anonymous>)
    at r (commons.js:1)
    at <anonymous>
(anonymous) @ commons.js:1
commons.js:1 ws::_onMessage {"jsonrpc":"2.0","method":"parity_subscription","params":{"result":{"":{"meta":"{\"description\":\"\",\"passwordHint\":\"\",\"timestamp\":1522528175529}","name":"TEST2","uuid":"39f03bc6-3306-ab1c-3238-cef143833a5f"},"":{"meta":"{\"descrdescri\":\"POST POST etc split fund ad\",\"passwordHint\":\"\",\"tags\":[\"old\"],\"timestime\":15\":1507333117546}","name":"Tokens","uuid":"077d1670-8b85-df7c-eed2-a17317345bd4"},"":{"meta":"{\"description\":\"\",\"passwordHint\":\"keepass\",\"tags\":[\"mining\"],\"timestamp\":1505584533826}","name":"parity-storj-poseidon","uuid":""},"":{"meta":"{\"description\":\"\",\"passwordHint\":\"\",\"timestamp\":1522527121568}","name":"TEST","uuid":"ae2f793d-663b-6bbe-8ef8-13155f75f18c"},"":{"meta":"{\"description\":\"Ledger Nano S\",\"hardware\":{\"manufacturer\":\"Ledger\"},\"tags\":[\"hardware\"],\"timestamp\":1507311678732}","name":"Nano S"},"":{"meta":"{}","name":"","uuid":""},"":{"meta":"{}","name":"","uuid":""},"":{"meta":"{\"abi\":[{\"constant\":false,\"inputs\":[{\"name\":\"_owner\",\"type\":\"address\"}],\"name\":\"removeOwner\",\"outputs\":[],\"type\":\"function\"},{\"constant\":false,\"inputs\":[{\"name\":\"_addr\",\"type\":\"address\"}],\"name\":\"isOwner\",\"outputs\":[{\"name\":\"\",\"type\":\"bool\"}],\"type\":\"function\"},{\"constant\":true,\"inputs\":[],\"name\":\"m_numOwners\",\"outputs\":[{\"name\":\"\",\"type\":\"uint256\"}],\"type\":\"function\"},{\"constant\":true,\"inputs\":[],\"name\":\"m_lastDay\",\"outputs\":[{\"name\":\"\",\"type\":\"uint256\"}],\"type\":\"function\"},{\"constant\":false,\"inputs\":[],\"name\":\"resetSpentToday\",\"outputs\":[],\"type\":\"function\"},{\"constant\":true,\"inputs\":[],\"name\":\"m_spentToday\",\"outputs\":[{\"name\":\"\",\"type\":\"uint256\"}],\"type\":\"function\"},{\"constant\":false,\"inputs\":[{\"name\":\"_owner\",\"type\":\"address\"}],\"name\":\"addOwner\",\"outputs\":[],\"type\":\"function\"},{\"constant\":true,\"inputs\":[],\"name\":\"m_required\",\"outputs\":[{\"name\":\"\",\"type\":\"uint256\"}],\"type\":\"function\"},{\"constant\":false,\"inputs\":[{\"name\":\"_h\",\"type\":\"bytes32\"}],\"name\":\"confirm\",\"outputs\":[{\"name\":\"\",\"type\":\"bool\"}],\"type\":\"function\"},{\"constant\":false,\"inputs\":[{\"name\":\"_newLimit\",\"type\":\"uint256\"}],\"name\":\"setDailyLimit\",\"outputs\":[],\"type\":\"function\"},{\"constant\":false,\"inputs\":[{\"name\":\"_to\",\"type\":\"address\"},{\"name\":\"_value\",\"type\":\"uint256\"},{\"name\":\"_data\",\"type\":\"bytes\"}],\"name\":\"execute\",\"outputs\":[{\"name\":\"_r\",\"type\":\"bytes32\"}],\"type\":\"function\"},{\"constant\":false,\"inputs\":[{\"name\":\"_operation\",\"type\":\"bytes32\"}],\"name\":\"revoke\",\"outputs\":[],\"type\":\"function\"},{\"constant\":false,\"inputs\":[{\"name\":\"_newRequired\",\"type\":\"uint256\"}],\"name\":\"changeRequirement\",\"outputs\":[],\"type\":\"function\"},{\"constant\":true,\"inputs\":[{\"name\":\"_operation\",\"type\":\"bytes32\"},{\"name\":\"_owner\",\"type\":\"address\"}],\"name\":\"hasConfirmed\",\"outputs\":[{\"name\":\"\",\"type\":\"bool\"}],\"type\":\"function\"},{\"constant\":true,\"inputs\":[{\"name\":\"ownerIndex\",\"type\":\"uint256\"}],\"name\":\"getOwner\",\"outputs\":[{\"name\":\"\",\"type\":\"address\"}],\"type\":\"function\"},{\"constant\":false,\"inputs\":[{\"name\":\"_to\",\"type\":\"address\"}],\"name\":\"kill\",\"outputs\":[],\"type\":\"function\"},{\"constant\":false,\"inputs\":[{\"name\":\"_from\",\"type\":\"address\"},{\"name\":\"_to\",\"type\":\"address\"}],\"name\":\"changeOwner\",\"outputs\":[],\"type\":\"function\"},{\"constant\":true,\"inputs\":[],\"name\":\"m_dailyLimit\",\"outputs\":[{\"name\":\"\",\"type\":\"uint256\"}],\"type\":\"function\"},{\"inputs\":[{\"name\":\"_owners\",\"type\":\"address[]\"},{\"name\":\"_required\",\"type\":\"uint256\"},{\"name\":\"_daylimit\",\"type\":\"uint256\"}],\"type\":\"constructor\"},{\"anonymous\":false,\"inputs\":[{\"indexed\":false,\"name\":\"owner\",\"type\":\"address\"},{\"indexed\":false,\"name\":\"operation\",\"type\":\"bytes32\"}],\"name\":\"Confirmation\",\"type\":\"event\"},{\"anonymous\":false,\"inputs\":[{\"indexed\":false,\"name\":\"owner\",\"type\":\"address\"},{\"indexed\":false,\"name\":\"operation\",\"type\":\"bytes32\"}],\"name\":\"Revoke\",\"type\":\"event\"},{\"anonymous\":false,\"inputs\":[{\"indexed\":false,\"name\":\"oldOwner\",\"type\":\"address\"},{\"indexed\":false,\"name\":\"newOwner\",\"type\":\"address\"}],\"name\":\"OwnerChanged\",\"type\":\"event\"},{\"anonymous\":false,\"inputs\":[{\"indexed\":false,\"name\":\"newOwner\",\"type\":\"address\"}],\"name\":\"OwnerAdded\",\"type\":\"event\"},{\"anonymous\":false,\"inputs\":[{\"indexed\":false,\"name\":\"oldOwner\",\"type\":\"address\"}],\"name\":\"OwnerRemoved\",\"type\":\"event\"},{\"anonymous\":false,\"inputs\":[{\"indexed\":false,\"name\":\"newRequirement\",\"type\":\"uint256\"}],\"name\":\"RequirementChanged\",\"type\":\"event\"},{\"anonymous\":false,\"inputs\":[{\"indexed\":false,\"name\":\"_from\",\"type\":\"address\"},{\"indexed\":false,\"name\":\"value\",\"type\":\"uint256\"}],\"name\":\"Deposit\",\"type\":\"event\"},{\"anonymous\":false,\"inputs\":[{\"indexed\":false,\"name\":\"owner\",\"type\":\"address\"},{\"indexed\":false,\"name\":\"value\",\"type\":\"uint256\"},{\"indexed\":false,\"name\":\"to\",\"type\":\"address\"},{\"indexed\":false,\"name\":\"data\",\"type\":\"bytes\"},{\"indexed\":false,\"name\":\"created\",\"type\":\"address\"}],\"name\":\"SingleTransact\",\"type\":\"event\"},{\"anonymous\":false,\"inputs\":[{\"indexed\":false,\"name\":\"owner\",\"type\":\"address\"},{\"indexed\":false,\"name\":\"operation\",\"type\":\"bytes32\"},{\"indexed\":false,\"name\":\"value\",\"type\":\"uint256\"},{\"indexed\":false,\"name\":\"to\",\"type\":\"address\"},{\"indexed\":false,\"name\":\"data\",\"type\":\"bytes\"},{\"indexed\":false,\"name\":\"created\",\"type\":\"address\"}],\"name\":\"MultiTransact\",\"type\":\"event\"},{\"anonymous\":false,\"inputs\":[{\"indexed\":false,\"name\":\"operation\",\"type\":\"bytes32\"},{\"indexed\":false,\"name\":\"initiator\",\"type\":\"address\"},{\"indexed\":false,\"name\":\"value\",\"type\":\"uint256\"},{\"indexed\":false,\"name\":\"to\",\"type\":\"address\"},{\"indexed\":false,\"name\":\"data\",\"type\":\"bytes\"}],\"name\":\"ConfirmationNeeded\",\"type\":\"event\"}],\"wallet\":true,\"timestamp\":1511645733491,\"deleted\":false,\"tags\":[\"wallet\"],\"description\":\"Nanopool\",\"name\":\"Nanopool\"}","name":"Nanopool"},"":{"meta":"{}","name":"","uuid":"f4ae9421-f147-47a9-9b76-532b43e5f604"},"0x":{"meta":"{}","name":"","uuid":""},"0x":{"meta":"{\"description\":\"Mine to here please ;\",\"passwordHint\":\"fuck off\",\"tags\":[\"mining\"]}","name":"Mining","uuid":""}},"subscription":"0xecda2449120ea9bb"}} SyntaxError: Unexpected string in JSON at position 92
    at JSON.parse (<anonymous>)
    at commons.js:1
    at Array.reduce (<anonymous>)
    at r (commons.js:1)
    at commons.js:1
    at t.value (commons.js:1)
value @ commons.js:1
`

the `ws::_onMessage {"jsonrpc":"2.0","method":"parity_subscription","params":{"result":{` error repeats multiple times. 

then `Uncaught SyntaxError: Unexpected string in JSON at position 92
    at JSON.parse (<anonymous>)
    at index.9c522a6db2.js:1
    at Array.reduce (<anonymous>)
    at r (index.9c522a6db2.js:1)
    at Object.callback (index.9c522a6db2.js:1)
    at e.value (inject.js:1)
index.9c522a6db2.js:1 could not register SW after 2.5s
(anonymous) @ index.9c522a6db2.js:1
index.9c522a6db2.js:1 Uncaught TypeError: Cannot read property 'address' of undefined
    at new e (index.9c522a6db2.js:1)
    at new t (index.9c522a6db2.js:1)
    at d._constructComponentWithoutOwner (vendor.js:1)
    at d._constructComponent (vendor.js:1)
    at d.mountComponent (vendor.js:1)
    at Object.mountComponent (vendor.js:1)
    at d.performInitialMount (vendor.js:1)
    at d.mountComponent (vendor.js:1)
    at Object.mountComponent (vendor.js:1)
    at Object.updateChildren (vendor.js:1)
index.9c522a6db2.js:1 Uncaught TypeError: Cannot read property 'address' of undefined
    at new e (index.9c522a6db2.js:1)
    at new t (index.9c522a6db2.js:1)
    at d._constructComponentWithoutOwner (vendor.js:1)
    at d._constructComponent (vendor.js:1)
    at d.mountComponent (vendor.js:1)
    at Object.mountComponent (vendor.js:1)
    at d.performInitialMount (vendor.js:1)
    at d.mountComponent (vendor.js:1)
    at Object.mountComponent (vendor.js:1)
    at Object.updateChildren (vendor.js:1)

in regards to the service worker message, I dont understand as it is creating a worker ...

creating new accounts will not cause them to show in the app

I'm running parity 1.10.0 on Ubuntu 16.04 LTS. I'm running parity under user parity. my user name is a member of group parity.
to get parity signer new-token to work, I have to run with sudo. When I pasted the new token into the popup, the UI froze and these errors showed up in the console for chrome 59.

bundle.js:1 ServiceWorker error Error: ServiceWorker is not available in your browser.
    at bundle.js:1
    at Object.<anonymous> (bundle.js:1)
    at t (bundle.js:1)
    at Object.<anonymous> (bundle.js:1)
    at t (bundle.js:1)
    at Object.<anonymous> (bundle.js:1)
    at t (bundle.js:1)
    at Object.<anonymous> (bundle.js:1)
    at t (bundle.js:1)
    at Object.<anonymous> (bundle.js:1)
(anonymous) @ bundle.js:1
bundle.js:1 UI version 0.1.1
bundle.js:1 js-ui: i18n in `ContextProvider` disabled
get @ bundle.js:1
bundle.js:1 setupWorker TypeError: s is not a constructor
    at r (bundle.js:1)
    at t.setupWorker (bundle.js:1)
    at t.default (bundle.js:1)
    at bundle.js:1
    at Object.<anonymous> (bundle.js:1)
    at t (bundle.js:1)
    at Object.<anonymous> (bundle.js:1)
    at t (bundle.js:1)
    at bundle.js:1
    at bundle.js:1
(anonymous) @ bundle.js:1
chrome-extension://kmendfapggjehodndflmmgagdbamhnfd/u2f-comms.html Failed to load resource: net::ERR_NOT_IMPLEMENTED
bundle.js:1 Ledger:checkJSSupport false
bundle.js:1 Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('chrome-extension://kmendfapggjehodndflmmgagdbamhnfd') does not match the recipient window's origin ('null').
(anonymous) @ bundle.js:1
bundle.js:1 WebSocket connection to 'ws://127.0.0.1:8546/' failed: Error during WebSocket handshake: Unexpected response code: 403
value @ bundle.js:1
bundle.js:1 ws:onClose
bundle.js:1 WebSocket connection to 'ws://127.0.0.1:8546/' failed: Error during WebSocket handshake: Unexpected response code: 403
value @ bundle.js:1
bundle.js:1 ws:onClose
bundle.js:1 WebSocket connection to 'ws://127.0.0.1:8546/' failed: Error during WebSocket handshake: Unexpected response code: 403
value @ bundle.js:1
bundle.js:1 ws:onClose

From @p-s-dev openethereum/parity-ethereum#8551

Version: Parity/v1.10.2-beta-f4ae813-20180423/x86_64-macos/rustc1.25.0
OS: macOS
installed: PKG release
fully synchronized?: no
Did you try to restart the node?: yes

Once "Start at Logon" is turned on, it can not be toggled-off.

expected:

The "Start at Logon" open can be enabled and disabled

I'm running:

• Parity client version: Parity/v1.10.3-stable-b9ceda3-20180507/arm-linux-gnu/rustc1.25.0
• Parity UI version: 0.1.1
• Operating system: MacOS
• Installed via: installer
• Fully synchronized: no
• Network: ethereum
• I tried to restart both Parity UI and Parity Ethereum client: yes

Hello, how to connect to parity client running on the different machine? Previously I connected via 192.168.0.xxx:8180 but now I need to connect via this app. I don't see an option to enter different URL