Hi Gourav,
Thank you for reporting this issue. I was able to replicate the error messages that you are seeing using the information that you’ve shared earlier. I’ll check this together with my teammates and will give you an update as soon as we have our findings.
Regards,
|
||||||
Hi Gourav,
Thanks for following up.
The team confirms that this warning is occurring, however it is harmless and can be ignored. Next update of the Android SDK should remove this warning, you can keep an eye on our release history for updates. Also, the ALL_ADS_COMPLETED event is an acceptable place to call adsLoader.release().
Regards,
Hi Gourav,
The SDK version 3.21.4 has been released with the fix below. Let me know if this version would solve the issue on your end.
- Removes a harmless warning message related to calling adsLoader.release() after the webview has been destroyed.
Regards,
Hi Gourav,
Thank you for your confirmation and for sharing this information. I’m going to check this with the team and will let you know for any feedback.
Regards,
Hi Gourav,
At the moment we do not have an update yet, but I’m going to check this with the team. I’ll let you know for any feedback.
Regards,
Hi Gourav,
I appreciate your patience and understanding on this matter. However, I’m afraid we do not have any update at this moment. But let me check this with the team and will let you know for any updates.
Regards,
BaseDisplayContainer
as well as the underlying WebView. This
should occur after disposing of the BaseManager using BaseManager.destroy()
and after the
manager has finished its own cleanup, as indicated by AdEvent.AdEventType.ALL_ADS_COMPLETED"
Hi Gourav,
Thanks for bringing this to our attention. For our test reference, could you share with us a sample project file demonstrating this exception error? This could be a new issue that is not related to the one you’ve reported initially.
Regards,
|
||||||