From 9f9fbc9605b75e6f1bebdf035dd50e37c4e45977 Mon Sep 17 00:00:00 2001 From: Jonathan Dixon Date: Wed, 28 Aug 2013 20:29:39 -0700 Subject: Fix for 10530176 - CookieSyncManager must be created by WebView c'tor WebViewClassic created the CookieSyncManager instane as a side effect of starting up its internal WebCoreThread. As this forms part of th API contract (app doesn't need to call CookieSyncManager.createInstance if it already made a WebView instance) promote this logic up to the API layer. Change-Id: I0e92d97be987dfef90162ad379c79b066aae34e0 --- core/java/android/webkit/WebView.java | 2 ++ 1 file changed, 2 insertions(+) (limited to 'core/java/android/webkit/WebView.java') diff --git a/core/java/android/webkit/WebView.java b/core/java/android/webkit/WebView.java index 1b57d50..3923539 100644 --- a/core/java/android/webkit/WebView.java +++ b/core/java/android/webkit/WebView.java @@ -498,6 +498,8 @@ public class WebView extends AbsoluteLayout ensureProviderCreated(); mProvider.init(javaScriptInterfaces, privateBrowsing); + // Post condition of creating a webview is the CookieSyncManager instance exists. + CookieSyncManager.createInstance(getContext()); } /** -- cgit v1.1