SAFE Network Dev Update - April 16, 2020

Thanks for another great update Maidsafe devs. Will play later with the new goodies. I’ve managed a week ago to even send testnet safecoin :stuck_out_tongue: try it out kids it’s super fun

12 Likes

@Haigha I’ve been able to replicate the connection issues on an Android v6.0 emulator - thanks for the tip! Logged here for further investigation.

Note that I’ve not yet been able to replicate the crash you saw.

Looks like that Xamarin link in the readme has indeed moved - will get that updated.

Thanks!

9 Likes

Thanks for taking note. Can you please tag me, if you remember, when it has been fixed. I am not completely sure how to follow bugs progress, well I have an idea, but not a whole lot of time to follow/understand technical details. Thanks again. (The crashing could just be my phone, e.g. i cant upload pics online due to a “low memory” error which is not true).

4 Likes

Will note to do so :+1:

2 Likes

@StephenC

So, I just had a similar experience and had an three time iteration through the select shared section (or authenticator app)… but it works the third time.

I wonder then that this is because I turned on the wifi and I note that above Haigha has both wifi and mobile signal connected. Given that I already had the connection file, perhaps it was easier to keep trying through to a success. Still there’s a user experience issue but it might centre on the handling of which signal is being used - wifi or mobile, choose wisely; or manage where is swaps back and forward??

This is @Haigha image above then showing both connections… and it was this Connect popup that bounced back for me to the Authentication options to select.

4 Likes

Good eye @davidpbrown :+1: . I gave that a shot.

First wifi only :frowning:
Then, mobile data only :frowning:

Worth trying but still receive the same error.

3 Likes

My last thought is did you try a few times… something intermittent about my instance of the same.

:+1: Will do…but in the morning…:canned_food: :sleeping:

1 Like

I tried 3 times on mobile data only and three times on wifi only…same error :man_shrugging: .

I think the next step for me would be to find and install the android authenticator and see if that works on my version…

2 Likes

=>

https://github.com/maidsafe/safe-authenticator-mobile/releases/tag/0.3.0

3 Likes

beautiful!! question is,… it means we don’t need parsec anymore? will you replace parsec with this AT2?If this AT2 is asset transfer system without consensus, then why we need parsec?

1 Like

:neutral_face:

I downloaded the net.maidsafe.SafeAuthenticator.apk from Github.

Installed, selected create account, created password, created passphrase

Popup says “Connecting to SAFE Network”

After a while I get this error:

When I close the authenticator app and then reopen it to retry I get this message:

I click on “Settings” which brings me to:

I click on download, which downloads a file (this file doesn’t show up in my downloads) and brings the app to this:

As the choice is already selected I have no other choice except to hit “back”, I could select “+” but wouldn’t know what to add.

When I go “back” I am brought back to the initial page (login/create account). I create a new account and am again brought to the original error (first screenshot).

Again, Android version 6.0.1. I made sure I was on wifi only this time. I hope I got the order of events correct. I will try again tonight. Cheers.

4 Likes

Can you update this? I have no problems but I am on 8.0.0 Samsung 7 Samsung Experience v9.0

1 Like

Upgrading Android typically is about getting a new phone :thinking:

2 Likes

Ah sorry my bad - I have just been accepting the system updates that happen every 3-4 months.
My phone is at least 3 years old - was a company hand-down.

Bottom right is three dots… Settings… should show the app version… is it 0.5.0?

2 Likes

Dont see the three dots…but went into android/settings/apps/safe… and saw it is 0.3.0

1 Like

Good news then… always nice to close off an odd problem.
Phone Settings then and App force stop and uninstall… then reinstall from https://github.com/maidsafe/safe-mobile-browser/releases

Ok, will try later. That link above should be updated then i presume…

Link above is good… likely you had conflict with having it already installed and perhaps not as yet a remove previous version action.

So, this leads to the same with also option on the AppCenter as well as github