Add a workaround to ensure that the WebViewDatabase and JniUtil can
still be initialized as side effect of making a CookieSyncManager
This was collateral damage from the fixes for Bug
10932261
Change-Id: If5ba65a7822d5b0afc14139dd84125058bf96897
if (context == null) {
throw new IllegalArgumentException("Invalid context argument");
}
+ // TODO: Remove this workaround after webview classic is no longer supported.
+ if (WebViewFactory.getProvider().getClass().getName().contains("WebViewClassic")) {
+ WebViewDatabase.getInstance(context);
+ }
setGetInstanceIsAllowed();
return getInstance();