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
Developer Community or GitHub 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.
Description of Problem: Use of identical code and values to connect to Windows Azure message bus works on MonoTouch, but not MonoDroid.
Steps to reproduce the problem:
1. Execute the code shown in "additional information" with proper Azure values under MonoTouch.
2. Execute the same code in MonoDroid.
Actual Results: It runs and returns a response on MonoTouch, but not on MonoDroid.
Expected Results: It should return the same value both places, rather than just dying on MonoDroid.
How often does this happen? Every time, but only been able to test it with my own messages buses.
The last gets a result every time on MonoTouch, but never on MonoDroid.
public string GetToken (string issuerName, string issuerSecret)
var acsEndpoint = "https://" + serviceNamespace + "-sb." + acsHostName + "/WRAPv0.9/";
var realm = "http://" + serviceNamespace + "." + sbHostName + "/";
var values = new NameValueCollection ();
values.Add ("wrap_name", issuerName);
values.Add ("wrap_password", issuerSecret);
values.Add ("wrap_scope", realm);
var webClient = new WebClient ();
var response = webClient.UploadValues (acsEndpoint, values);
This bug might be no longer around (very likely) but if you could provide a full repro application (with project for both Xamarin.Android and Xamarin.iOS) that still fails in the current versions of the product that would let me investigate the issue.
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!