Preventing Concurrent login III : GameSparks

Start a new topic

Answered

Preventing Concurrent login III

Eric Moncada

started a topic almost 5 years ago

Hi,

This is to follow that topic, but I can't answer the postso I o pen a new one.

I did Call Spark.getPlayer().disconnect(true); in the AuthenticationResponse

Very often I have this error :

{"stackTrace":"\tat 296608-response-AuthenticationResponse:5\n","error":"TypeError: Cannot call method \"disconnect\" of null (296608-response-AuthenticationResponse#5)","script":"AuthenticationResponse"}

How can the Spark.getPlayer() be null in the AuthenticationResponse ?

How can I fix that ?

Thanks !

Best Answer

Customer Support said almost 5 years ago

Hi Eric,

The only way you'd get null in the AuthenticationResponse would be if there was an error Authenticating, examples of this would include using an invalid token for a social auth or a bad userName/password combination. I can see quite a few failed FacebookConnectReqeusts in your game, they look like they're linked to the access token so you should start your investigations there.

Thanks,

Liam

1 Comment

Customer Support

said almost 5 years ago

Answer

Hi Eric,

Thanks,

Liam

How can we help you today?