You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 19, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 19, 2026. It is now read-only.
ButtonClicker: Class not found when unmarshalling #17
When I build and run the c++ ButtonClicker example, and create a room, I get this in the device log.
(Note: the room creation does seem to succeed, and I can see the room, and launch the match.)
Can you share:
what version of play services you are running on the device?
What version of the client lib are you including when building?
What version of the Play Games app running on the device?
This is the a scary looking exception that actually has no impact on the functionality. Apparently Samsung inspects intents which can trigger the message.
Activity
stolk commentedon Sep 11, 2015
This is still present in GPG v2.0
stolk commentedon Sep 17, 2015
Could it be possible that it is a SAMSUNG bug?
I test on Samsung devices.
Is the unmarshalled file from google play, or from android?
http://developer.samsung.com/forum/board/thread/view.do?boardName=General&messageId=272802
claywilkinson commentedon Sep 17, 2015
Can you share:
what version of play services you are running on the device?
What version of the client lib are you including when building?
What version of the Play Games app running on the device?
stolk commentedon Sep 17, 2015
Play Games version 3.2.21
GPG v2.0
Google Play Services rev 26
claywilkinson commentedon Sep 17, 2015
Thanks - I'll pass it along and let you know what they find out.
stolk commentedon Feb 4, 2016
Any update on this? I still get these:
EDIT: Just tried with gpg-cpp-sdk_2.1: this is still there.
claywilkinson commentedon Mar 31, 2016
This is the a scary looking exception that actually has no impact on the functionality. Apparently Samsung inspects intents which can trigger the message.