Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
In reference to case #29385
In Mono 2.10.12, the BasicHttpBinding property no longer supports EnableHttpCookieContainer because it is Depreciated. The replacement is AllowCookies, but this property does not work. Upon inspection of the source code the following line is found:
The HttpCookieContainerBindingElement is added in accordance with EnableHttpCookieContainer, but not AllowCookies.
Same problem here, I just updated Xamarin with the stable release and it still contains this bug. The company I work for can't go on with it like this...
Same problem here, using Xamarin.iOS 18.104.22.168 with iOS 7.
Is there any plans to fix this?
Created attachment 7110 [details]
## Steps to reproduce
1. Follow the steps on  to set up and run the "WcfService1" solution from the attached test case in IISExpress.
2. Once "WcfService1" is running, open the "Clients" solution.
3. Set either the Android or iOS project as the startup project.
4. Change the IP address and port in the call to `new Service1Client()` to match the address and port you set up for "WcfService1" in step 1.
5. Run the Android or iOS project (on simulator or device).
6. Tap the "Send Cookies" button, and wait for the text view to display "Sent cookies."
7. Tap the "Read Cookies" button.
The text view will display:
"Server sent back cookie: Key=NA, Value=NA"
## Expected result
The text view should display the same result as the "Console" test app (on Mono 3.4.0 or .NET):
"Server sent back cookie: Key=Company, Value=Xamarin"
## Version Information
Created attachment 7112 [details]
Here's a patch that allows the test case from comment 4 to run successfully on both Xamarin.iOS and Xamarin.Android.
Based on this result, it seems that the conditional compile logic at  is no longer needed for Xamarin.iOS or Xamarin.Android.
Thanks for the patch, applied!
Did it make to the last release? I don't see setting AllowCookies in my code fixes the problem.
The test case from comment 4 works correctly as of the current beta versions:
These versions will be moving to the stable channel soon.
The current stable versions do _not_ include the patch:
*** Bug 21889 has been marked as a duplicate of this bug. ***