SelfKeyFoundation / Identity-Wallet

Code for the SelfKey Identity Wallet
https://selfkeyfoundation.github.io/Identity-Wallet/
MIT License
57 stars 26 forks source link

V 1.6.4 macOS Transaction Failed Not Enough ETH #2375

Closed NorseGaud closed 4 years ago

NorseGaud commented 4 years ago

When I Export Log File, where do I find it? I can't seem to find it.

Screen Shot 2020-08-29 at 8 40 36 PM Screen Shot 2020-08-29 at 8 38 34 PM

macOS 10.15.6 Selfkey IdenWal V 1.6.4

sk91 commented 4 years ago

@NorseGaud Hi, thank you for reporting this.

Can you please provide logs for this? They are located in ~/Library/Logs/SelfKey\ Identity\ Wallet/

Have a nice day! )

NorseGaud commented 4 years ago

log.log

sk91 commented 4 years ago

hi @NorseGaud,

I couldn't find a definitive answer from the log. We had an issue though with ethereum network connectivity for several hours, and it's clear from the log that you had been affected by it.

Your issue might be related to it.

Can you try to do it again?

Thanks!

NorseGaud commented 4 years ago

Hmm, I've tried a few more times, all spread out, and it seems to still be throwing it. The cost of the DID has changed but not enough to exceed the ETH balance I have (~$116 vs the ~$20 for the DID).

sk91 commented 4 years ago

Hey @NorseGaud,

Can we try to do it again?

Please do the following:

And then attach the log file here if it fails

Thanks

NorseGaud commented 4 years ago

Sure thing!

log.log-v2.log

NorseGaud commented 4 years ago

It's very interesting... I run the following and see the 15:02:27:781 error before I hit the GET DID button:

2020-09-07 15:01:57:438 MAIN main error: unhandled rejection, FetchError: request to http://127.0.0.1:21325 failed, reason: connect ECONNREFUSED 127.0.0.1:21325
2020-09-07 15:02:20:297 MAIN Menu warn: SUPPORT: ISSUE REPRODUCTION STARTS HERE
2020-09-07 15:02:24:675 MAIN relying-party error: Error establishing session StatusCodeError: 422 - {"message":"Invalid signature"}
2020-09-07 15:02:24:854 MAIN kyc-duck error: getSession HD StatusCodeError: 422 - {"message":"Invalid signature"}
2020-09-07 15:02:25:042 MAIN relying-party error: Error establishing session StatusCodeError: 422 - {"status":"Unprocessable Entity","error":"INVALID_INPUT_ERROR"}
2020-09-07 15:02:25:229 MAIN kyc-duck error: getSession HD StatusCodeError: 422 - {"status":"Unprocessable Entity","error":"INVALID_INPUT_ERROR"}
2020-09-07 15:02:25:422 MAIN relying-party error: Error establishing session StatusCodeError: 422 - {"status":"Unprocessable Entity","error":"INVALID_INPUT_ERROR"}
2020-09-07 15:02:25:611 MAIN kyc-duck error: getSession HD StatusCodeError: 422 - {"status":"Unprocessable Entity","error":"INVALID_INPUT_ERROR"}
2020-09-07 15:02:25:838 MAIN relying-party error: Error establishing session StatusCodeError: 422 - {"status":"Unprocessable Entity","error":"INVALID_INPUT_ERROR","details":"Unprocessable Entity"}
2020-09-07 15:02:26:055 MAIN kyc-duck error: getSession HD StatusCodeError: 422 - {"status":"Unprocessable Entity","error":"INVALID_INPUT_ERROR","details":"Unprocessable Entity"}
2020-09-07 15:02:26:786 MAIN kyc-duck error: Error loadRelyingParty Error: Session is not established
2020-09-07 15:02:26:789 MAIN kyc-duck error: Error loadRelyingParty Error: Session is not established
2020-09-07 15:02:27:317 MAIN kyc-duck error: Error loadRelyingParty Error: Session is not established
Right before I hit the GET DID --> 2020-09-07 15:02:27:781 MAIN kyc-duck error: Error loadRelyingParty Error: Session is not established

Then, clicking GET DID doesn't show any other logs until I close the error window that says Transaction Failed. Here is what is seen after close:


2020-09-07 15:03:10:958 MAIN Web3Service error: Web3Service provider error Error: Could not find block
2020-09-07 15:03:15:339 MAIN relying-party error: Error establishing session StatusCodeError: 422 - {"status":"Unprocessable Entity","error":"INVALID_INPUT_ERROR"}
2020-09-07 15:03:15:494 MAIN kyc-duck error: getSession HD StatusCodeError: 422 - {"status":"Unprocessable Entity","error":"INVALID_INPUT_ERROR"}
2020-09-07 15:03:15:666 MAIN relying-party error: Error establishing session StatusCodeError: 422 - {"message":"Invalid signature"}
2020-09-07 15:03:15:840 MAIN kyc-duck error: getSession HD StatusCodeError: 422 - {"message":"Invalid signature"}
2020-09-07 15:03:16:080 MAIN relying-party error: Error establishing session StatusCodeError: 422 - {"status":"Unprocessable Entity","error":"INVALID_INPUT_ERROR","details":"Unprocessable Entity"}
2020-09-07 15:03:16:255 MAIN kyc-duck error: getSession HD StatusCodeError: 422 - {"status":"Unprocessable Entity","error":"INVALID_INPUT_ERROR","details":"Unprocessable Entity"}
2020-09-07 15:03:16:430 MAIN relying-party error: Error establishing session StatusCodeError: 422 - {"status":"Unprocessable Entity","error":"INVALID_INPUT_ERROR"}
2020-09-07 15:03:16:601 MAIN kyc-duck error: getSession HD StatusCodeError: 422 - {"status":"Unprocessable Entity","error":"INVALID_INPUT_ERROR"}
2020-09-07 15:03:17:366 MAIN kyc-duck error: Error loadRelyingParty Error: Session is not established
2020-09-07 15:03:17:460 MAIN kyc-duck error: Error loadRelyingParty Error: Session is not established
2020-09-07 15:03:17:809 MAIN kyc-duck error: Error loadRelyingParty Error: Session is not established
2020-09-07 15:03:18:198 MAIN kyc-duck error: Error loadRelyingParty Error: Session is not established
2020-09-07 15:03:31:229 MAIN Web3Service error: Web3Service provider error Error: Could not find block
2020-09-07 15:03:35:340 MAIN Web3Service error: Web3Service provider error Error: Could not find block
2020-09-07 15:03:51:459 MAIN Web3Service error: Web3Service provider error Error: Could not find block```
sk91 commented 4 years ago

@NorseGaud thous errors are not related, they just say you don't have a DID yet

Can you share what kind of wallet are you using? Trezor, Ledger, Key - Pair ?

NorseGaud commented 4 years ago

I think I did a generate wallet from the app along time ago. I just use the private key to get into the account

NorseGaud commented 4 years ago

Ok, something is.. weird... I can use the full private key 0xXXXXXXXXXXXXXXXXXXXXXXXXXXX (with 0x) and ALSO without 0x (just the XXXXXXXXXXXXXXXXXXX part).

I just realized that the private key without 0x I don't actually have access to... So SelfKey allowed me to log in with an invalid private key (without 0x)...

Can you guys prevent the use of a private key that doesn't include 0x? The "0x" that shows up in the Private Key login is EXTREMELY confusing and made me think I didn't have to use 0x.

sk91 commented 4 years ago

Ok @NorseGaud, now it makes sense :)

This issue was fixed (not released yet)

Check out this issue https://github.com/SelfKeyFoundation/Identity-Wallet/issues/2343 to recover access

NorseGaud commented 4 years ago

THANK YOU!!!!!