Multiple 'Set-Cookie' header values in HTTP response are not respected on Android RN 0.60.5

[pinstripe-potatohead]

Multiple 'Set-Cookie' header values in HTTP response are not respected on Android RN 0.60.4 - only the last one shows up in JS. Multiple 'Set-Cookie' headers are concatenated into a string (correctly) on iOS.

React Native version: 0.60.5

[chenyanfei-m]

Same problem in v0.59.8

[ronyv]

any updates on this ? is this a bug with react native or is it not a good practice to set multiple 'Set-Cookie' headers ?

[pinstripe-potatohead]

@ronyv Please look at #23005 and #21795 . AFAIK, multiple Set-Cookie headers are allowed by the spec. This is a bug with React Native Android. Downgrading to v0.59 will allow you to use the userNativeAccessor workaround

[ronyv]

@pinstripe-potatohead : I don't think downgrading the RN version is a good idea, considering the stability & other enhancements that the newer versions provides. I am wondering why this still remains as unresolved when these are something fundamental.

@hramos : any comments on this ?

[chenyanfei-m]

add

import com.facebook.react.bridge.ReadableNativeArray;
import com.facebook.react.bridge.ReadableNativeMap;

ReadableNativeArray.setUseNativeAccessor(true);
ReadableNativeMap.setUseNativeAccessor(true);

in MainApplication.java can resolve it.

[ronyv]

@chenyanfei-m : what you suggested is just a workaround for RN versions < 0.60. . I am using 0.60.5 and this is not working. I just don't want to downgrade my RN version for resolving this issue. Rather i will consider some other efficient alternative. Hope RN will fix this fundamental issue in the upcoming releases.

@ronyv Hello brother. Did you solve the issue? I still fighting with it, and any help would be great.