-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'releasing leaked death recipient' caused by gms. #29
Comments
And here is the full log, for context. Play Games version Android 4.4.4 gpg-cpp-sdk_2.0
|
Also caused by |
I am using app evaluation package:
I get such a terrible error log !!! (((
|
still have the issue! |
Lmaoo no one really replied after 5 years |
I didn't know that computers had a "Link to Death." I thought it was only humans that had that... lmao. |
I'm facing the same issue mentioned above currently in Android 11, Flutter version 3.30, InAppReview version 2.0.4 |
RoomServiceClient is deprecated, don't use it. in_app_review is not part of the cpp-android-basic-samples nor Play Games services offering. Please file bugs for in_app_review in the in_app_review issue tracker. linkToDeath is part of Android IPC. It allows one process receive a call in case "linked" process was killed. See https://developer.android.com/reference/android/os/IBinder#linkToDeath(android.os.IBinder.DeathRecipient,%20int) |
Please audit the gms code.
I see this on the console log when a room gets connected:
It's an issue caused by com.google.android.gms
The text was updated successfully, but these errors were encountered: