REGISTER_WAITING_ROOM_LISTENER_RESTRICTED

[jknight-nc]

We trigger a load from the cloud when the app is reforegrounded. We get a foreground event on return from Google Play's Invite Player to Realtime activity. So when we return from Googles Matchmaker UI, we trigger a load from Google Play Games Snapshot API. This Cloud Load is breaking the Realtime matchmaking with the following error message:

11-16 16:54:35.175 20353 15760 E RSCStateMachine: REGISTER_WAITING_ROOM_LISTENER_RESTRICTED: when not in room
11-16 16:54:35.178 21851 21851 E WaitingRoom: Room ChAKCAjX5PbJThACEAEYAyABEOCqlPPQ6sG_uQE invalid. Finishing activity.

The waiting room UI fails suddenly and silently, delivering no useful information to the client app through the SDK's error callbacks. The Matchmaker returns through the success callback with the room in AUTOMATCHING state or INVITING state. No one ever joins the room, and the client times out.

If we dont cloud load at that time. Everything works. The bug seems to be internal to the Google SDK. At the very least the waiting room UI callback should contain an ERROR for this. Currently it reports a "success".

[Talabo]

Have you solved this? I seem to experience the same

[jknight-nc]

We disabled the Cloud Save during Multiplayer and reenable it afterwards.

[Talabo]

Could you be more spesific? I've not yet started to use any Cloud Save function in my application. I'm experiencing this problem when trying to either start a "quick match", invite players. I can see the waitRoom for a fraction of a second and it's gone. The error gets called twice.

Did you notice this problem after updating Google play services in recent months?
I had a build that worked perfectly in August. Figured out to continue on it and now I'm experiencing the same as you.

I will control this with a sample code, to be sure I didn't do anything wrong in the build.