A previous question question implies that altering the Cookie Jar isn't possible. Is there at least a way to pass parameters in the header of the webcall ie:for authentication.
Asked
Active
Viewed 2,044 times
1 Answers
0
I did the following and when I inspect the request that is made, it looks like my "Cookie" header is getting replaced by Chrome custom tabs even though my "Value" header goes through.
Bundle headersBundle = new Bundle();
headersBundle.putString("Value", value);
headersBundle.putString("Cookie", cookie);
CustomTabsIntent customTabsIntent = CustomTabsIntent.Builder().build();
customTabsIntent.intent.putExtra(android.provider.Browser.EXTRA_HEADERS, headersBundle);
intent.launchUrl(context, uri);
This answer does not provide a source but it says that it is not possible to alter the cookie jar on Chrome Custom Tabs currently.
Edit:
And this answer recommends using Smart Lock for Passwords on Android to perform authentication in custom tabs.

B W
- 692
- 1
- 8
- 21