-
Notifications
You must be signed in to change notification settings - Fork 106
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
Bug continuation "AppLovinFullscreenActivity memory leak on Android version 14 #683" #734
Comments
@LevGloba thanks for reaching out.
|
I apologize, the issue is reproducible only starting with Android version 14 and above. Steps to reproduce the issue: In SDK versions (14.0.0 and later) Call load and then display ad (reward or interstitial) from fragment, when onAdHidden method is called, reward or interstitial call destory method and then fragment is closed. Then open fragment, repeat steps above and close. |
@LevGloba Thanks for the additional details. Could you also share a sample project where it is reproducible as well since it is not reproducible on our demo app. That would be helpful for us to reproduce on our end and take a look. |
@alvarshahanji. I created a project where this issue also occurs. Link to the project: https://github.com/LevGloba/memory-leak-problem-in-appolowing |
@LevGloba looks like this is a known memory leak on Android U (14) https://issuetracker.google.com/issues/294776102 |
@alvarshahanji, I've checked and issues memory leak only on the android 14. What do you do with this information, which you've gave? |
MAX SDK Version
13.0.0
Device/Platform Info
Android (14), Google pixel 6-8
Current Behavior
The bug was fixed in the Apollo demo application, but not fixed in the working library itself.
Expected Behavior
It is expected that Apollo in Full Screen Activity will be destroyed
How to Reproduce
On Android version 13-14. Call loading, and then display advertising from the fragment, after showing the advertisement and when it is hidden, close the fragment and ad. Then open the fragment, repeat the steps described above and close.
Reproducible in the demo app?
No
Additional Info
The text was updated successfully, but these errors were encountered: