new user successfully completing FacebookConnectRequest does not trigger RegistrationResponse
O
One More Turn
started a topic
over 6 years ago
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 collectionplayerDirectory
from what I understand, FacebookConnectRequest is supposed to register new users just as RegistrationRequest does. Why isn't RegistrationResponse being called then?
Best Answer
B
Baris Tumerkan
said
over 6 years ago
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.
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
B
Baris Tumerkan
said
over 6 years ago
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.
One More Turn
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?
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.
- Oldest First
- Popular
- Newest First
Sorted by Newest FirstOne More Turn
worked perfectly thanks guys!
Customer Support
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
Baris Tumerkan
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
-
Documentation Notes
-
Design issues with user events
-
Using NoSQL
-
Runtime Collections vs Metadata Collections
-
Anonymous authentication from browser app
-
Modules
-
Movement With Unity
-
Problem with url parameters for downloadables
-
Querying NoSql GameSparks database
-
Challenge accesType
See all 2487 topics