iOS setCookie about gtm-oauth2

[GoogleCodeExporter]

If FetchHistory is built in, that will go away because the selector will be 
implemented by the app.  But if you only need OAuth2 without the fetchers 
history, that could be a problem.  We'll take a look, renaming it might ripple 
to other things, we will have to check.

Original comment by [email protected] on 29 Sep 2014 at 1:54

[GoogleCodeExporter]

Yes, thats what i was thinking. Let me know what your checks show and if 
renaming it will work, although i'm sure it is named setCookies in order to be 
compatible with an NS class for cookie logic. Id prefer not to lose any cookie 
functionality if possible.

Thanks.

Original comment by [email protected] on 30 Sep 2014 at 1:32

[GoogleCodeExporter]

The same problem I faced. We commented the call of setCookies. 

Original comment by [email protected] on 2 Feb 2015 at 12:17