Looking back at what
@Greg Breinholt posted - I suspect that the issue is caused when you're using a custom leaderboard & getting the data for it via the LoadLeaderboardMetadata function call. The reason is (I think) that this call invokes the PendingResultWrapper & the PendingResultWrapper source appears to make several references to classes that have been removed from the GPGS API. When the PendingResultWrapper raises the result event in B4A, it maps the result to the corresponding class - & it just so happens that the first mapping attempt is to the CancelMatchResult class, which is why you're seeing that error.
I think that if you used the standard GPGS leaderboards, you wouldn't see this issue. I've been using the standard GPGS leaderboards & achievements for years & haven't made any changes since they deprecated the multiplayer functions, but not seen any issues because of it.
At first glance of the source, it looks like if you removed all the mapping attempts to deprecated classes from the PendingResultWrapper, that would (possibly) resolve the issue - however doing so might also break other parts of the library. I can't say for sure because I haven't had time to look at it closely.
- Colin.