Written for webnative 0.35-0.36
In most cases this should be avoided, but in case you do want to risk it, here’s how you reset your filesystem.
NOTE: This could change at any time. If by the time you read this a lot of time has passed since us posting this, ask us to review this post before you undertake this reset.
Steps
- Go to the Fission Drive app
- Open up the browser console
- Type the following in the console.
fs = await wn.FileSystem.empty({ account: fs.account, eventEmitter: fs.eventEmitter, dependencies: fs.dependencies, rootKey: fs.root.privateNodes["private/"].key }) await fs.mkdir({ directory: [ wn.path.RootBranch.Private, "Apps" ] }) await fs.mkdir({ directory: [ wn.path.RootBranch.Private, "Audio" ] }) await fs.mkdir({ directory: [ wn.path.RootBranch.Private, "Documents" ] }) await fs.mkdir({ directory: [ wn.path.RootBranch.Private, "Photos" ] }) await fs.mkdir({ directory: [ wn.path.RootBranch.Private, "Video" ] }) await fs.publish()
- Wait till publish is finished (you should see
DNSLink updated
) - Sign out of Drive (either by clicking sign out in menu, or clearing website data in dev tools)
- Sign back in.
In case fs.root.privateNodes["private/"].key
fails, you can also get the rootKey
from the auth lobby. There you would run await myReadKey()
in the dev console to get it.