Bug 207546 - WKHttpStore does NOT sync until WKProcessPool is destroyed
Summary: WKHttpStore does NOT sync until WKProcessPool is destroyed
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit API (show other bugs)
Version: WebKit Nightly Build
Hardware: iPhone / iPad All
: P2 Blocker
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2020-02-11 06:46 PST by Brandon
Modified: 2020-02-19 00:18 PST (History)
9 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Brandon 2020-02-11 06:46:21 PST 
When a web-page sets cookies, the cookies are reflected in the next request from the WKWebView. This works fine. However, if we try to access the cookies from WKWebView via the WKHttpCookieStore or from NSHTTPCookieStorage or from WKWebsiteDataStore. fetchDataRecordsOfTypes:completionHandler

The cookies are NOT there. However, if we set the `WKProcessPool` to  a new process pool, and then attempt to access the cookies, they are immediately flushed to disk and can be accessed.
Comment 1 Radar WebKit Bug Importer 2020-02-11 09:22:31 PST 
<rdar://problem/59350764>
Comment 2 Sihui Liu 2020-02-14 15:07:45 PST 
(In reply to Brandon from comment #0)
> When a web-page sets cookies, the cookies are reflected in the next request
> from the WKWebView. This works fine. However, if we try to access the
> cookies from WKWebView via the WKHttpCookieStore or from NSHTTPCookieStorage
> or from WKWebsiteDataStore. fetchDataRecordsOfTypes:completionHandler
> 
> The cookies are NOT there. However, if we set the `WKProcessPool` to  a new
> process pool, and then attempt to access the cookies, they are immediately
> flushed to disk and can be accessed.

Can you attach a test app for us to look into?