Support Topics Documentation Slack YouTube Blog

User is already logged in from another device/computer

Are you looking for help?

I am not able to login using Backendless system.

Backendless Version (3.x / 5.x, Online / Managed / Pro )

Do not know where to check.

Client SDK (REST / Android / Objective-C / Swift / JS )

Swift

Application ID

F2FE78BB-5D08-44FE-B074-6E7C29B49B03

Expected Behavior

Able to log in.

Actual Behavior

I get an error: User is already logged in from another device/computer. The application is configured to disable multiple concurrent logins with the same user credentials.

Enable Multiple Logins is disabled (Secondary login set as logout and notify the first user), because we do not want multiple logins. We want the last session to be deactivated and the new one activated when logging in.

Solution needed.

Hello,

We’ll investigate this issue and answer as soon as possible.

Regards,
Olha

Unfortunately I cannot reproduce this issue (tried to login using 3 different devices and no error occured).
Could you please provide the steps (preferably with code snippet) to reproduce this issue?

Regards,
Olha

Hi,

It’s just a basic login operation Backendless.shared.userService.login, which results in errorHandler being called with the fault object. fault.message says: “User is already logged in from another device/computer. The application is configured to disable multiple concurrent logins with the same user credentials.”

It’s working for me now as well, but this is happening randomly from time to time.

Can you check your logs?

Otherwise, how can we resolve this if it’s a random occurance?

Thanks.

For more details, do you use the stayLoggedIn = true property?

No, we’re not using it.

Hi,

Got the same error just now. I did not correctly enter the password and the account was locked out, then I re-enabled the account and got the error when trying to login again: “User is already logged in from another device/computer. The application is configured to disable multiple concurrent logins with the same user credentials.”. I was not even logged in previously…

Hi @Invited

Thank you for providing additional informations, however I tried it several times to reproduce the problem (with REST) and no luck.

Anyways, there is an internal ticket BKNDLSS-22883 to investigate the issue, and our IOS engineer will take a look into this as soon as possible.

If you do not mind could you please answer for the following questions, they are also might be helpful to find the reason:

  1. did you recently changed your “Login Settings” ?
  2. could you please prepare for a test user to test this case?
  3. it happens with all users or with a specific one?

Regards, Vlad

Hello,

Swift-SDK uses REST API for requests.
@Invited I’ve tried to reproduce this steps in your APP

I did not correctly enter the password and the account was locked out, then I re-enabled the account and got the error when trying to login again: “User is already logged in from another device/computer. The application is configured to disable multiple concurrent logins with the same user credentials.”. I was not even logged in previously…

but with no luck.
Everything works fine.
Could you please answer Vladimir’s questions to clarify details?

Regards,
Olha

Hi,

Thanks Olha. As I mentioned, this is happening randomly without any obvious pattern. After waiting a few minutes I can login again without any issues.

Answering Vladimir’s questions below:

  1. did you recently changed your “Login Settings” ?

No.

  1. could you please prepare for a test user to test this case?

Sure. I’ll DM you the credentials.

  1. it happens with all users or with a specific one?

Happened to 2 users.

Hello,

I’ve tried to login with credentials you’ve sent us and everything works without any issues.
Could you please attach a simple sample project (just with login) that reproduces this issue because we cannot reproduce it.

Regards,
Olha

As I mentioned, this happens randomly so a sample project will not help. That’s why this is extremely frustrating.

Can you verify your logs? I will post here as soon as I encounter the issue again.

The error message is coming from your API, so you should be able to track the conditions on why this error is returned.

Thanks.

We don’t see any problems in our logs, please add them on your side.
Also, please provide an example that reproduces this issue at lease once - we’ll run it in a loop for tests.