Works like that… but unexpected it’s not alao with focus.
I’ll leave the design feedback on the vault selection page for the experts to take into consideration I’ll log in the meantime so this feedback isn’t missed.
Updated the OP so that for Android it is the GH links that show first. Look out for the expand option at the bottom of the release to find the apk
I am/will be logging bugs, suggestions etc on the GH project board for either the authenticator or browser, so won’t reply to everything in here separately. Will be checking up on comments periodically.
Appreciate all the feedback & comments, keep them coming!
State?.. each time I goto the Authenticator it’s asking I login and hasn’t remembered the browser was allowed… and the browser isn’t making obvious progress loading //primer or complaining that it has no connection.
While typing primer page has completed… though I’d just created another account and not yet authorized the browser… so, last authentication still live in browser. Browser isnt obvious about its having authorized state… some icon missing for that perhaps.
So, it’s the initial setup account page that is not offering scroll on focus … or without focus… passphrase and password pages.
On the Authenticator appearing to ask for login again - that sounds like a known issue logged here.
I tried loading
safe://primer and it worked for me, took maybe 2-3 seconds or so. I also saw a progress bar the whole time (something that I’d flagged as a bug during development as initially no progress bar was showing anywhere - was fixed). Hopefully any delay in loading & lack of progress bar you saw was temporary. Will look out for this and see if I can replicate again.
The issue you point out about after having logged in as a different user, the last authenticated session is still in progress is an interesting one. I never really considered it as a bug/problem but I can see now that this could cause confusion, lead to somebody posting something as the wrong user, etc. I’ll log that and see if we can find a way to make it clear who is logged in during a session, or kill the session if the authenticator is logged out at any point.
EDIT - as Ravinder points out here the browser uses an unregistered session, so not a problem.
So, browser restarted and nice and smooth to authenticate with an Authenticator that looks not logged in… and it worked to become authorized and visit to primer proves that. So, concern if I have two accounts with different intent for control of apps.
Also, surprised the browser fell over… not many other apps open etc and none other do fall down. Is there option to grab bug feedback that’s useful?
@davidpbrown, the authenticator uses an unregistered session. That means it’s just reading the connection info from the authenticator app. You don’t need to login in to the authenticator to allow the browser to connect to the network. or you don’t even need an account.
Also, in the browser we have re-authenticate option in the right bottom menu popup control which can be used to refresh the session (especially when you want to connect to the different vault)
Ah yes… of course. I disengage thinking when testing
In response to the crash post - if you open the browser again and go to
App logs then you can hopefully send us the logs where the crash happened
I think the crash maybe related to the browser trying to fetch multiple or lots of data at once in parallel. If I remember correctly, I think the primer has lots of images that maybe causing some kind of high memory consumption and then OS stops/prevents the app so it doesn’t consume any more memory then allowed/allocated to the browser app.
I think, based on logs and feedbacks + device specs like memory and processor, in coming releases I can improve the logic to handle the multiple data request and that will solve this.
Thanks @savage, I’m feeling much better now.
It’s loading , but you wouldn’t be able to create a web app from the mobile browser, not yet cause it’s using an unregistered session and currently we don’t have an interface/bridge for node/JS APIs enabled in the mobile browser. But, I’m sure we will have that some day
I’m sure you mean, soon
Cheers for that, I only started working on that UI last night and haven’t had a chance to fiddle around with the SAFE browser on mobile yet - I didn’t want to waste time making assumptions about the @css-media values I would need so I just left it unstyled. Expect that to be much more friendly by, say, Friday.
I think, I can pull that off but I’ll definitely need a long break after that
I was thinking about asking, then thought we got plenty already and would leave that question for another day.
I once tried to create a POC to check if it’s achievable with our current setup (https://github.com/ravinderjangra/safe-mobile-browser/tree/JSinterface/SafeMobileBrowser) and I was able to make this work (like for one or two APIs) but then we deprecated all the older APIs and put a stop on this so we don’t repeat the efforts with the new APIs. I hope this will still work and I’ll not have to start from scratch.
10¹⁰⁰ times thank you Maidsafe devs,
You can’t imagine how super charged, I feel to be on the SAFE Network again.
Maybe when tapped on anywhere have it select deselect and show the check in the circle and have a trash can to the far right for deletion, triggering the delete prompt.
I’m having some issues with the Authenticator I’ll have to test on another device and share later.
Huge compliments on the ease of downloading and picking the configuration file, I too was confused by having to specifically tap that little circle to select the file and being shown the delete prompt instead. I’m persistant so I figured it out but should be a little more intuitive.
The apps look amazing with the material update!