WebView Illegal Argument Exception Crash

[reactipsum]

My app is presenting content in Webview.

But nowadays i have an issue. My app is crashing due to cookie value. I have shared stacktrace on below.

Fatal Exception: java.lang.IllegalArgumentException Unexpected char 0xdc at 343 in Cookie value

okhttp3.Headers$Builder.checkNameAndValue (Headers.java:320)
okhttp3.Headers$Builder.set (Headers.java:300)
okhttp3.Request$Builder.header (Request.java:163)
okhttp3.internal.http.BridgeInterceptor.intercept (BridgeInterceptor.java:86)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.java:92)
okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept (RetryAndFollowUpInterceptor.java:124)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.java:92)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.java:67)
okhttp3.RealCall.getResponseWithInterceptorChain (RealCall.java:170)
okhttp3.RealCall.access$100 (RealCall.java:33)
okhttp3.RealCall$AsyncCall.execute (RealCall.java:120)
okhttp3.internal.NamedRunnable.run (NamedRunnable.java:32)

[JayElPo]

Hello,

I have the same problem when the cookie contains characters: à, é, è, etc.

My cookie :
Fatal Exception: java.lang.IllegalArgumentException
Unexpected char 0xe0 at 1949 in Cookie value:
....
CookiePaymentEvar5=evar5=Souscription à la carte CUP - NVX;
....

Regards,

[hramos]

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

• Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
• If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
• Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.