LocationToAccountId reverse AccountId to Location can't distinguish

[zqhxuyuan]

current there're AccountId32Aliases inside LocationToAccountId, we add another RelayChainAccountId32Aliases type in orml PR.

both of those two struct type can reverse AccountId to MultiLocation, thus only the first one will take effect. for example: if we configure with order (AccountId32Aliases, RelayChainAccountId32Aliases), then reverse AccountId on LocationToAccountId resulting (0, AccountId32). there'er no chance to get into (1, AccountId32) only if we configured with order (RelayChainAccountId32Aliases, AccountId32Aliases), but at the same time, the latter configure also cause no chance to get into (0, AccountId32).

Also I've checked polkadot codebase, seems there're no usercase invoking reverse() method on LocationToAccountId, Am I right?

[KiChjang]

This sounds like it's an issue that can be solved on your chain with a custom implementation of Convert<MultiLocation, AccountId>. You must come up with a heuristic that allows you to determine whether or not the resulting MultiLocation must have 1 parent or not.

Closing as I don't think there's anything that needs to be done on the Polkadot side.