Parallel Ledger account overwrites Polkadot Ledger account on Polkadot-JS UI

[Juanma0x]

To replicate this scenario, follow the steps below:

1. Install the Polkadot Ledger app with version 23.9420.2.
2. Install the developer version of the Parallel Ledger app, specifically version 17.189.9.
3. Add the Polkadot Ledger account to either the Polkadot-JS UI, or use the Polkadot extension.
4. Next, add the Parallel Ledger account.

The outcome of these steps is as follows:

• Polkadot-JS UI or the Polkadot extension will display the Parallel Ledger account while the Polkadot Ledger account will no longer be visible.
• Conversely, if the Polkadot Ledger account is added, the Parallel Ledger account will disappear.

Desired outcome:

• Both accounts should be able to be added to either Polkadot-JS UI and the Polkadot extension, coexisting.

Context: From the issue opened on Zondax/ledger-parallel

[...] I can tell you that this is an UI/UX issue and the app is ok. Since Parallel and Polkadot use the same derivation path, the pubkey is the same and probable polkadot-js just detects that and doesn't compare the addresses. [...]

[jacogr]

Sadly this is something I cannot replicate, and that not investigate nor fix (if there is indeed an issue) -

Don't have access to Ledger, so cannot do step 1 nor step 2

Having said that, Ledger accounts should only be visible based on the genesisHash, i.e. only available on networks with the specified genesis.

If this continues being an issue, a PR is appreciated, i.e. something that is tested on the contributing side.

And yes, if the underlying pubkey is the same, there will only be one address - the UI certainly does not differentiate based on encoding of the address and never will. Fot the same pubkey there will only ever be a single entry, this is expected and intended.