I’m attempting to use the “restricted users” feature where a device-specific access code is required in order to use the app. I had tinkered with this option a few months ago (with DAB 11.1.1) and it worked.
But when I try it now a few months later with an app built with DAB 12.0, on the “administrator” device when I attempt to add a user and generate an access code, after the “submit” button, I receive a pop-up dialog with the error message: “Sorry, we were unable to sign in to the database server.”
If you’re asking for a git repo would it be safe to guess you have android studio… or at least some way to unpack an .apk? I just worked through a problem getting web based audio to stream in a DAB dictionary. It turned out that marking the audio as coming from an internet source didn’t add <uses-permission android:name="android.permission.INTERNET" /> to the AndroidManifest.xml, which was necessary for the app to access the online audio repository. I’m presuming that the default is for DAB to create the .apk without that permission. It could be that by clicking the the radio buttons that require device access codes or registration in security>restriction, it is meant to add internet permission to the manifest, but has the same problem as setting the audio from an internet source.
One way I found that I could force internet permission into the manifest was by adding analytics. There could be other ways but I haven’t tried. No idea if your APK’s inability to sign in is because of lack of internet permission or lack of access to the database for other reasons. But maybe it’s one thing to double check.
Hi Dave,
Thanks for the idea! Unfortunately, I checked AndroidManifest.xml as you suggested and I am seeing the line you mentioned which grants internet permissions. The troubleshooting continues.
Hi Dave,
Your idea gave me another thing to try though, which worked successfully! In that menu, there was an enabled checkbox for “require an internet connection when adding users.” I disabled this checkbox, rebuilt the app, and now I don’t see that error message.
I don’t think disabling this checkbox has any adverse effects for us? It still requires a user to have an access code, and allows administrator devices to generate it. Seems like it should be fine.
Developers: any idea why even though the android manifest includes internet permissions when this box is checked, the app gives a message “unable to sign into the database server?”
