From 050c552f096a6f8f2283162edcb9c6b015cfb3dd Mon Sep 17 00:00:00 2001
From: Jonathan Dixon <joth@google.com>
Date: Fri, 4 Oct 2013 13:01:47 +0100
Subject: Fix CookieSyncManager for WebViewClassic

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
---
 core/java/android/webkit/CookieSyncManager.java | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/core/java/android/webkit/CookieSyncManager.java b/core/java/android/webkit/CookieSyncManager.java
index 13aa43f..154a290 100644
--- a/core/java/android/webkit/CookieSyncManager.java
+++ b/core/java/android/webkit/CookieSyncManager.java
@@ -89,6 +89,10 @@ public final class CookieSyncManager extends WebSyncManager {
         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();
-- 
cgit v1.1