- Adding a serialized cookie for a URL in a cookie store, which is attached to the cookie request header for the outgoing request.
- Clearing all cookies from the cookie store.
How cookies are stored
WebView manages cookies by keeping temporary session cookies in active memory for fast access, while securely saving persistent cookies to the app’s private storage directory. Persistent cookies are those with specific expiration dates. Developer inspect and manipulate this stored state by enabling remote debugging and using the Chrome DevTools application panel on connected device. This interface provides a way to view all active cookies on your current origin (the page’s scheme, domain, and port), allowing you to live-edit values, manually clear data, and verify important security attributes likeHttpOnly, Secure, and SameSite are applied correctly.
To troubleshoot why a cookie isn’t behaving as expected, switch to the DevTools Network panel to monitor the Cookie and Set-Cookie headers exchanged during network requests. This helps you identify rejected cookies, syntax errors, and cross-site policy violations.
Cookie manager details
A cookie object can have the following fields:Adding a URL cookie in the cookie store
Clearing all cookies in the cookie store
- The
set()method sets a single cookie for the URL. - For any existing cookie with the same name, the host and path are replaced. The Domain value sets the host of the cookie as described in this Set-Cookie doc.
- The cookie store ignores expired cookies.
- The WebView instance shares the cookie store. Different apps don’t share the cookie store. A common engine, which includes the cookie store, shares multiple WebView instances in the same app.
- The React Native layer of the app can’t read the cookie store at this point.

