Fetched cookies doe not have expires field on Android

[achen0115]

RN: 0.63.2
Library version: 3.0.0 (also upgraded to 4.0.1, but it does not work either)

I could fetch cookies successfully on Android, but they do not contain expires field, even I set the expiration when saving the cookie.

e.g.

CookieManager.set(theUrl, {
  "domain": ".somesite.com", 
  "expires": "2030-05-30T12:30:00.00-05:00", 
  "name": "AuthenticationToken", 
  "path": "/", 
  "value": "my_token_value", 
  "version": ""
})

I got the following when I called CookieManager.get(theUrl)

{
  "AuthenticationToken": {
    "httpOnly": false,
    "path": null,
    "value": "my_token_value",
    "secure": false,
    "domain": null,
    "name": "AuthenticationToken"
  }
  ...other cookies
}

PS: Path and domain are not returned correctly either on Android as reported in #67.

[shorsher]

Hey @achen0115, curious if you ever solved this issue?

[shorsher]

After looking at the Android cookie manager docs (https://developer.android.com/reference/android/webkit/CookieManager), this is actually expected behavior. Internally the cookie manager keeps track of the state (expiration, etc.), but the return value of getCookie() returns "value the cookies as a string, using the format of the 'Cookie' HTTP request header", which does not include expiration, path, httpOnly, etc.

However, internally, it seems that CookieManager manages expiration, etc and those values are passed into WebView appropriately.

[peterlazar1993]

I dug into this on a newer version(13.2.2), as @shorsher mentions, getCookie does not give the raw cookie, but if you inspect the cookie via the WebView inspector, you can see that the cookie has the right expiry value.

But I did have to set the expiry value with this format explicitly yyyy-MM-dd'T'HH:mm:ss.SSSXXX, came to this conclusion after looking at the native code.

[muhammadarsal]

@peterlazar1993 @shorsher hey there! :) I observed that react-native-webview sets the cookie expiration to 'Session' and does not regard the expires value passed. I am wondering what good is the internal management of cookie expiration if the webview cannot get the expiration date. Did you ever find a workaround for this issue?