tuum-tech / identify

MIT License
7 stars 3 forks source link

Initialization of DIDDoc fails (except in rare cases) #74

Closed pauldesmondparker closed 11 months ago

pauldesmondparker commented 11 months ago

Description

Chromium 116.0.5845.96 Arch Linux
branch: master
Metamask Flask 10.34.4-flask.0

Cannot get the Account Info to populate, fails on entry of account id. One (1) works, two (2) does not. image image image

Remediation

[!Note] It has been intermittently possible to remove flask; 1. add hedera testnet network, 2. import testnet account; and then it would work. But that hasn't worked consistently.

Reproduce

  1. Fresh git clone
  2. yarn install && yarn start
  3. remove and install flask
  4. connect :white_check_mark:
  5. send hello message :negative_squared_cross_mark:

[!Important] {code: -32603, message: "Error while trying to get the account: Error: Coul…era account info using the accountId '0.0.487338'" ...}

https://hashscan.io/testnet/account/0.0.487338

kpachhai commented 11 months ago

Are you connecting to this hedera account via metamask account or external account? In other words, is this a metamask account or a non-MetaMask account as described here? https://docs.tuum.tech/identify/tutorials/hedera-hashgraph

Also what's the identity snap version that's being used? Recently, we released a new version 1.5.0.

pauldesmondparker commented 11 months ago

My bad. My mistake.

Also what's the identity snap version that's being used? Recently, we released a new version 1.5.0. image

I'm using an external account, but got the accountId from the ED25519 account mixed up with the ECDSA account.

[!Note] I imported my account into metamask with the private key from (4). Which gave the account (1). But then I used accountId (2) instead of (3)

image