SNApp v0.0.6-alpha.8-linux

Support
1

Downloaded this and chmod +x 'd it.

Starts fine, due to some dubiety about connecting to shared-section I clicked on Safe Browser install

Told me it had to restart to complete then didn’t…

willie@gagarin:~/projects/maidsafe$ ./safe-network-app-v0.0.6-alpha.8-linux-x64.AppImage 
(node:104947) DeprecationWarning: file property is deprecated and will be removed in v5.
(node:104947) DeprecationWarning: file property is deprecated and will be removed in v5.
(node:104947) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(node:104947) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(electron) 'getName function' is deprecated and will be removed. Please use 'name property' instead.
(electron) 'setMovable function' is deprecated and will be removed. Please use 'movable property' instead.
(electron) 'setResizable function' is deprecated and will be removed. Please use 'resizable property' instead.
14:16:05.909%c ›
14:16:05.911%c ›
%c14:16:05.914 › {
  constructor: 'Error',
  stack: 'Error: Object has been destroyed\n' +
    '    at App.<anonymous> (/tmp/.mount_safe-nvDxK3N/resources/app.asar/app/webpack:/app/main.prod.js:4551:5)'
}
14:16:06.150%c ›
2

Now it upgraded itself as promised to v0.0.6-alpha.15 but simply dies
willie@gagarin:~/projects/maidsafe$ ./safe-network-app-v0.0.6-alpha.15-linux-x64.AppImage 14:28:55.087%c › (node:105566) DeprecationWarning: file property is deprecated and will be removed in v5. (node:105566) DeprecationWarning: file property is deprecated and will be removed in v5. (node:105566) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. (node:105566) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.

What extra logging can I turn on to find out more about this issue?

1 Like
3

@Southside you can start with the --debug arg to get more output

1 Like
4 
willie@gagarin:~/projects/maidsafe$ ./safe-network-app-v0.0.6-alpha.15-linux-x64.AppImage --debug
15:01:21.589%c ›
15:01:21.613%c ›
15:01:21.614%c ›
15:01:21.614%c ›
15:01:21.614%c ›
15:01:21.615 ›
15:01:21.615%c ›
15:01:21.616%c ›
15:01:21.616%c ›
15:01:21.616%c › null
15:01:21.617 ›
15:01:21.617%c › false
15:01:21.617%c › true
15:01:21.618%c › null
15:01:21.618%c › true
15:01:21.619%c › true
15:01:21.619%c › false
15:01:21.619%c › false
15:01:21.620%c ›
15:01:21.620%c ›
15:01:21.620%c ›
15:01:22.581 ›
15:01:22.600%c ›
(node:107163) DeprecationWarning: file property is deprecated and will be removed in v5.
(node:107163) DeprecationWarning: file property is deprecated and will be removed in v5.
(node:107163) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(node:107163) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
5

Hmm, nothing untoward there (beyond the logs not displaying properly, but that’s def not the issue at play here; and something i have on my list to look into :slight_smile: ).

Not sure what it could be. I’ll have a go on my machine here later and let you know if I can replicate or no

can you have a pgrep SAFE Network and see if anything is still running? Could be some processes didn’t end

1 Like
7

ooops – lots…

willie@gagarin:~$ pgrep safe
81513
81517
81524
81528
81532
81536
81540
81544
102516
104951
104955
104957
105102
105106
105119
105121
105146
105148
105151
105200
105208
willie@gagarin:~$ pkill -e safe
safe_vault killed (pid 81513)
safe_vault killed (pid 81517)
safe_vault killed (pid 81524)
safe_vault killed (pid 81528)
safe_vault killed (pid 81532)
safe_vault killed (pid 81536)
safe_vault killed (pid 81540)
safe_vault killed (pid 81544)
safe-authd killed (pid 102516)
safe-network-ap killed (pid 104951)
safe-network-ap killed (pid 104955)
safe-network-ap killed (pid 104957)
safe-network-ap killed (pid 105102)
safe-network-ap killed (pid 105106)
safe-network-ap killed (pid 105119)
safe-network-ap killed (pid 105121)
safe-network-ap killed (pid 105146)
safe-network-ap killed (pid 105148)
safe-network-ap killed (pid 105151)
safe-network-ap killed (pid 105200)
safe-network-ap killed (pid 105208)

So relaunching with – debug I get two dev tools windows and I saw the SNApp window flash briefly and disappear.

image
image1267×940 427 KB

If I launch without debug it comes up OK.

DO I still need to do networks switch shared-section and reauth etc ao should I try all that from within the SNApp?

Still not having much luck connecting to the shared section with the CLI but seems OK on mobile.

Im away out for an hour or so, no more feedback for a bit :slight_smile:

1 Like
8

Okay that’s good to know. Seems to chime with something we were seeing on windows w/ updates too.

You’d set up the shared section etc as normal. Snapp just uses the installed CLI / authd (or will prompt to install otherwise). Currently it doesnt handle updating /restarting etc, but it will eventually.

Thanks for digging in!

1 Like
9

I failed to log on to shared-section

image
image438×604 77.8 KB

more edits to come later…
FWIW I do not think this is SNApp specific, I think its a general auth failure somehow

10

That must be the exact same thing others have been seeing with CLI:

2 Likes
11

That’s what I was thinking myself. I’ll look harder tomorrow.
Thank you for all your work.

12

This topic was automatically closed after 60 days. New replies are no longer allowed.