This is my first attempt at doing some development with safenet, things seemed to go well to start with, but
I have some issues with authentication. It seems to be randomly logging me out and my accounts vanishes for no reason as well (I have to sign up again when it happens). My main issue is getting the app in the tutorial to work consistently when I refresh.
From console:
Error: Routing client error → Account does not exist for client
Versions:
- node 9.7.1
- npm 6.0.0
- windows 10 pro
- Peruse-v0.7.0-win-x64-dev
- safe_vault-v0.17.2-win-x64
What I did:
I followed this guide:
https://hub.safedev.org/platform/web/
I cloned the examples and my safenetwork.js now looks like this:
Step by step:
-
Started vault:
safe_vault.exe --first
output:
Running safe_vault v0.17.2
==========================
I 18-10-16 21:24:55.588375 Node(4e71f7…()) Started a new network as a seed node.
I 18-10-16 21:24:55.588876 Created chunk store at C:\Users\Warz\AppData\Local\Temp\safe_vault_chunk_store.EXa8N1eFPg8g with capacity of 2147483648 bytes. -
npm start
output:
safe_web_app_quick_start@1.0.0 start O:\wamp\www\maidsafe\safe_examples\safe_web_app_quick_start
neutrino start -
Started Peruse-v0.7.0-win-x64-dev\Peruse.exe
-
Tried to sign in with account secret and account password
output: Account does not exist
This seems to happen a lot.
So I go to create account and go through the whole procedure to sign up again
- Peruse Browser requests Auth Permission ACCEPT DENY:
I accept, the Peruse Browser icon appears under authorized apps
account status 9/1000
- I open a new tab in peruse browser and go to localhost:5000
- Warz Test webapp requests Auth Permission ACCEPT DENY:
I accept
- The script seems to work fine. The mutable entries appear, see: i.imgur DOT com/PMCKJX1.png
- I refresh and get the “Warz Test webapp requests Auth Permission ACCEPT DENY:” message again,
which I accept. - This time it does not work. The developer console log shows this error:
{message: “Core error: Routing client error → Account does not exist for client”, stack: “-101: Core error: Routing client error → Account …s\app.asar\node_modules\ffi\lib\callback.js:66:25”}message: "Core error: Routing client error → Account does not exist for client"stack: "-101: Core error: Routing client error → Account does not exist for client↵ at module.exports (Z:\executable\Peruse-v0.7.0-win-x64-dev\resources\app.asar\node_modules@maidsafe\safe-node-app\src\native_error.js:32:10)↵ at args.push.ffi.Callback.restArgs (Z:\executable\Peruse-v0.7.0-win-x64-dev\resources\app.asar\node_modules@maidsafe\safe-node-app\src\native_base.js:105:27)↵ at Z:\executable\Peruse-v0.7.0-win-x64-dev\resources\app.asar\node_modules\ffi\lib\callback.js:66:25"proto: Error
at makeError (Z:\executable\Peruse-v0.7.0-win-x64-dev\resources\app.asar\node_modules@maidsafe\safe-node-app\src\native_error.js:23:17)
at module.exports (Z:\executable\Peruse-v0.7.0-win-x64-dev\resources\app.asar\node_modules@maidsafe\safe-node-app\src\native_error.js:31:13)
at args.push.ffi.Callback.restArgs (Z:\executable\Peruse-v0.7.0-win-x64-dev\resources\app.asar\node_modules@maidsafe\safe-node-app\src\native_base.js:105:27)
at Z:\executable\Peruse-v0.7.0-win-x64-dev\resources\app.asar\node_modules\ffi\lib\callback.js:66:25
Promise rejected (async)
(anonymous) @ App.vue:40
Promise resolved (async)
(anonymous) @ App.vue:39
created @ App.vue:38
callHook @ vue.runtime.esm.js:2917
Vue._init @ vue.runtime.esm.js:4626
VueComponent @ vue.runtime.esm.js:4794
createComponentInstanceForVnode @ vue.runtime.esm.js:4306
init @ vue.runtime.esm.js:4127
createComponent @ vue.runtime.esm.js:5604
createElm @ vue.runtime.esm.js:5551
patch @ vue.runtime.esm.js:6126
Vue._update @ vue.runtime.esm.js:2656
updateComponent @ vue.runtime.esm.js:2784
get @ vue.runtime.esm.js:3138
Watcher @ vue.runtime.esm.js:3127
mountComponent @ vue.runtime.esm.js:2791
./node_modules/vue/dist/vue.runtime.esm.js.Vue.$mount @ vue.runtime.esm.js:7995
Vue._init @ vue.runtime.esm.js:4636
Vue @ vue.runtime.esm.js:4725
./src/index.js @ index.js:4
webpack_require @ bootstrap 31e00c9e07c4e93564e2:678
fn @ bootstrap 31e00c9e07c4e93564e2:88
0 @ safenetwork.js:60
webpack_require @ bootstrap 31e00c9e07c4e93564e2:678
./node_modules/ansi-html/index.js.module.exports @ bootstrap 31e00c9e07c4e93564e2:724
(anonymous) @ index.js:728
Screenshot: i.imgur DOT com/fxUXEzn.png
-
I navigate back to the other tab and refresh, I end up at
safe-auth://home/#/login and it’s asking me to sign in. -
I sign in, and it now looks like this: i.imgur DOT com/gVgnjR5.png (I notice account status is now 16/1000 instead of 9/1000).
-
I navigate back to the tab with localhost:5000 and refresh
-
I accept once again and get the same error as before (routing client error)
-
I go back to the other tab (safe-auth://home) and refresh. I am still logged in…
Ideas?