Sign In Register

How can we help you today?

Start a new topic
Answered

new user successfully completing FacebookConnectRequest does not trigger RegistrationResponse

the reproduction steps are pretty simple.


what works:

new users complete RegistrationRequest

RegistrationResponse then is triggered inserting their info my runtime collection named playerDirectory


what doesn't work:

new user uses FacebookConnectRequest

RegistrationResponse then is NOT triggered

the game trips over itself thinking that this new player is now in my runtime collection playerDirectory


from what I understand, FacebookConnectRequest is supposed to register new users just as RegistrationRequest does. Why isn't RegistrationResponse being called then?


Best Answer

I think the request response pairs like this are rather badly documented. 

You get an AuthenticationResponse triggered after a FacebookConnectRequest, whether or not it's a new player. You can check the "newPlayer" property there and trigger your custom player creation code there.





Answer

I think the request response pairs like this are rather badly documented. 

You get an AuthenticationResponse triggered after a FacebookConnectRequest, whether or not it's a new player. You can check the "newPlayer" property there and trigger your custom player creation code there.





1 person likes this

Hi One More Turn,


Only the RegistrationRequest will trigger a RegistrationResponse, every other method of authentication will trigger an AuthenticationResponse. As Baris mentioned you can check the "newPlayer" bool here and use it to trigger the creation of some custom player data when it comes back as "true". If you have any further questions just let me know.


Thanks,

Liam

worked perfectly thanks guys!

Login to post a comment