After a colleague of mine imported a user into our server, the user was unable to login through the Android app. The error message at login was that “This user is already logged in.” This happened continuously over several hours until escalated to me.
As it turns out, the usernames for these users were malformatted (had " "and “/”). When these were removed, the user was able to login.
So! Points are as follows:
- The user extended app from @eyeseetea seems to bypass username constraints. I assume this means that the same would be true for import/export of users, but I haven’t tested
- For android, is there a way to allow for 1 user to log in multiple times? Indeed, this is a common solution for us in particular for testing purposes on non-prod servers where we can set up a single user for data entry and pass credentials to multiple devices (all who sign in at the exact same time, more or less). We’ve never experienced any issues here on 2.8.2 nor 2.9.1.1; is there a possibility that we won’t be able to log in if users are already logged in?
- The sense of “already logged in” feels pretty vague for me, given Android will only ping the server when initially logging in, syncing configuration, syncing data, etc. But in general an android device can be “logged in” but, I’m assuming, would be “logged out” from timeout at the server level. Given the ambiguity here, I’m curious if this feature is something useful.