-
Notifications
You must be signed in to change notification settings - Fork 87
Open
Description
Issue details, reproduction steps/code
On the Android, when the application is restarted multiple times using back button (destroys activity but not application), despite calls to destroy, activity, reportfragment and some google class leaks remain in the memory dump.
If you remove the final attribute from the activity inside class PurchaseManagerGoogleBilling and assign activity to null in the destroy(), then the leaks disappear.
Version of gdx-pay and/or relevant dependencies
1.3.7
Stacktrace
Please select the affected platforms and payment service implementation
- Amazon
- googlebilling
- googlepay
- apple robovm
- Huawei
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels