Skip to content

Preload WebView provider on app startup #96

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.

Sign up for GitHub

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

Closed
MihaiCristianCondrea wants to merge 1 commit into from
Closed

Preload WebView provider on app startup #96

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions app/src/main/java/com/d4rk/androidtutorials/java/ads/managers/AppOpenAd.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@
import android.app.Application.ActivityLifecycleCallbacks;
import android.content.Context;
import android.os.Bundle;
import android.webkit.CookieManager;

import androidx.annotation.NonNull;
import androidx.annotation.Nullable;
Expand Down Expand Up @@ -36,6 +37,16 @@ public void onCreate() {
this.registerActivityLifecycleCallbacks(this);
MobileAds.initialize(this, initializationStatus -> {
});
// Pre-warm the WebView system on the main thread. Some ad SDK calls such
// as CookieManager.getInstance() may occur on background threads which
// can cause deadlocks if the WebView provider has not been initialized
// yet. Initializing it here prevents the "AdWorker" threads from
// blocking on WebViewFactory.getProvider.
try {
CookieManager.getInstance();
} catch (Exception ignored) {
// Ignore WebView initialization errors; ads will simply not use cookies.
}
ProcessLifecycleOwner.get().getLifecycle().addObserver(this);
appOpenAdManager = new AppOpenAdManager();
}
Expand Down