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 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.
Proxy issues are a huge wrench in Activation. We have essentially 0 support for them due to the limitations of the mono baked into the product binaries (mtouch/mandroid). This will be changing soon, and I've got word that Larry and Bojan have a plan to move the web integration to the IDE, which can take full advantage of the desktop mono / .NET on windows with it's superior proxy support.
Other than this, the message itself is not really a clue as to the underlying reason. I'll be putting together a list of questions or perhaps a script to make this information gathering easier.
This will be fixed with 4.10.1, but verification is required still. Upping priority.
I believe this may be part of the fixes you are working on.
So I'm not quite sure what the bug is. If the bug is that the user cannot activate because of proxies, we have proxy support now for at least some of the more common cases.
If the bug is the user's license is not picked up sometimes even though it is in the right place, that's not something that has been explicitly addressed by us because that is an issue in monodroid or monotouch, not the shared code.
So what should I do? Just close this?
It's hard to assess these types of bugs, as we're combining probably several behaviors into a few reports here from support. The best thing to do IMO is to deal with these issues in known chunks, and then gather more data to see if/how people are still hitting the issue.
In this case, there's a very clear explanation for many people which is that proxy support had not been added yet, so it's probably best to RESOLVE this, verify things during the proxy testing, and then gather more data from support to see if there's another category of issues we can solidify into a bug.
Setting to RESOLVED FIXED.