Today we are happy to announce that we’ve updated the SAFE Authenticator for mobile (Android and iOS).
The SAFE Authenticator acts as a gateway to the SAFE Network and allows you to control and manage what access and permissions that you give to other SAFE Apps.
Download the latest Android APK or get the source code to build it for yourself from our GitHub repo here!
So what’s changed?
Well, we’ve given the UI a complete refresh with highlights being:
Copy and paste the invitation token into the Invitation field on the Authenticator.
(this step is only required when creating an account to begin with)
Installs fine, onboarding screens respond fine, but once on the login page nothing responds to taps. All I can do is exit the app. Tried uninstall /re-install (as first install was an update) but no difference.
A couple of Android updates ago (I think) the method of allowing installation of apps from unknown sources changed from a single master setting to having to allow for each app trying to do the install.
I’ll see if I can find a better worded version of that…
Hey @happybeing
We were able to reproduce this issue on architecture armeabi-v7a when API level <23. The issue is with the android-ndk tool chain used to build the native libraries. We will get it sorted, update the SafeAuthenticator APK and get back to you.
Well it seems to work well on 16yo Lagavulin with Android 7.0 … but I couldn’t login to existing account… having transferred the password over USB to double check, I’m not sure what’s occurring that’s stopping it.
edit: Using a new invitation code (thanks @JPL) and creating a new account, it just works™!
Simple download and run, is ideal.
The only issue I saw from the functioning otherwise was that copying the invitation code, doesn’t present a pop that suggests the code has been copied to clipboard, which is always useful to see… but that is the website, so full marks for the Authenticator itself.
The other thought was the typing of a long password on the phone is a pina; so, hoping in future to be able to trigger a new account with fingerprint… given there’s no difference with a plain text password stored or typed in for real security of that.
The issue was with the way the native libraries used by the authenticator were built from safe_client_libs. We’ve updated the native libraries and fixed a few other minor bugs. For more information have a look at the change log.
However, we are still having an issue with supporting API level 16, you can find more information in the GitHub repository.
… but I couldn’t login to existing account… having transferred the password over USB to double check, I’m not sure what’s occurring that’s stopping it.
This includes the fix for the 