search

fission-codes / dashboard

The account dashboard for the Fission platform
https://dashboard.fission.codes
GNU Affero General Public License v3.0
8 stars 0 forks source link

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'cid') #46

Open vorburger opened 2 years ago

vorburger commented 2 years ago

https://dashboard.fission.codes remains stuck on https://auth.fission.codes for me. The console shows:

basic.ts:55 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'cid')
    at basic.ts:55:40
    at async Promise.all (/index 0)
    at async Object.JF (basic.ts:43:17)
    at async Function.fromInfo (PublicTree.ts:78:19)
    at async xn.getDirectChild (PublicTree.ts:167:11)
    at async xn.getOrCreateDirectChild (tree.ts:184:18)
    at async xn.mkdirRecurse (tree.ts:56:19)
    at async xn.mkdirRecurse (tree.ts:63:7)
    at async uc.runOnNode (filesystem.ts:655:16)
    at async uc.mkdir (filesystem.ts:215:5)

Desktop where I'm trying to login:

Smartphone where I've approved the login:

Additional context

When I first tried it, my Brave desktop browser used to have a local built-in IPFS Node activated. That seems to be conflicting with the IPFS Node of my https://dappnode.io. I've meanwhile Disabled Brave Desktop's built-in IPFS Node activated, but it's possible that Fission perhaps somehow got caught up in this and has some sort of corrupt local state? I'm happy to provide any additional information required if it helps you to make it more stable.

vorburger commented 2 years ago

FYI I can reproduce it on a New Private Window, which presumably (?) does not share state with the regular one.

matheus23 commented 2 years ago

Hi @vorburger 👋

This might be an instance of a known issue. Can you try running webnative.leave() in https://dashboard.fission.codes and re-trying?

If that doesn't fix it and you have another logged-in device around, please try clicking "remove this device" in the auth lobby of the affected device and re-linking.

Please let me know how that goes :+1:

vorburger commented 2 years ago

I managed to remove this device on the mobile, and logged in on the desktop browser using that file from the Recovery Kit.

I then tried to login on a New Private Window on the same desktop:

  1. open https://auth.fission.codes, which says: Authenticated as vorburger. Keep this window open if you want to authenticate on another device.
  2. Shift-Ctrl-N
  3. F12 to get Console
  4. Ctrl-L https://dashboard.fission.codes
  5. Click SIGN IN WITH FISSION
  6. It takes you to https://auth.fission.codes/?didExchange=did...
  7. Click Sign In
  8. Type Username and Click Link account
  9. Do these numbers match the ones shown on your other device?
  10. click Approve (on the other one)
  11. It asks Allow Dashboard access to the following for about 1 month?, click Yes
  12. Same error as above.
  13. webnative.leave() in Console (of https://auth.fission.codes) makes it say Authenticated as vorburger
  14. Ctrl-L https://dashboard.fission.codes
  15. Click SIGN IN WITH FISSION
  16. It takes you to https://auth.fission.codes/?didExchange=did...
  17. Click Sign In
  18. It asks Allow Dashboard access to the following for about 1 month?, click Yes
  19. It seems to just "hang" on Loading your filesystem (without any errors on the Console now)
  20. I give up after 1 minute or so, and try something else, in the same Dashboard tab of the still Private Window:
  21. Ctrl-L https://drive.fission.codes, Click SIGN IN WITH FISSION, click Yes to Allow
  22. Same error as above.
  23. webnative.leave() in Console (of https://auth.fission.codes) makes it say Authenticated as vorburger
    1. Ctrl-L https://drive.fission.codes
  25. New error, not sure if this is in any way related or a separate bug:
decode.js:120 Uncaught (in promise) Error: CBOR decode error: did not find any content to decode
    at tm (decode.js:120:11)
    at Cs (index.js:59:37)
    at Object.$F (encoded.ts:35:17)
    at async basic.ts:54:15
    at async Promise.all (/index 2)
    at async Object.JF (basic.ts:43:17)
    at async Function.fromInfo (PublicTree.ts:78:19)
    at async xn.getDirectChild (PublicTree.ts:167:11)
    at async xn.getOrCreateDirectChild (tree.ts:184:18)
    at async xn.mkdirRecurse (tree.ts:56:19)

This might be an instance of a known issue.

Do you want to link this to another bug?

It seems to be broken.