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.
Creating this bug report based on a forum thread:
This might be related to bug 22834 "When opening Android Project in Visual Studio, iOS Trial License Ended message pops up".
## Steps to reproduce
1. Log into a Xamarin account that has only a Xamarin.Android business subscription.
2. Create a new Xamarin.Android application in Visual Studio. (From the forum thread: "I do not have any iOS projects in my solution.")
3. Press the "Start debugging" button to attempt to build, deploy, and debug the application.
(Note: I have not yet had a chance to try to reproduce this problem myself.)
The activation dialog for Xamarin.iOS appears repeatedly:
> Using Xamarin.iOS with Visual Studio requires Business edition or higher.
> Purchase a Xamarin.iOS subscription
> Open the Xamarin Store in a web browser to purchase a subscription.
> Begin a Trial
> Get a free trial with access to all paid features.
> Continue using Starter Edition in Xamarin Studio on Mac
> You will not have access to this feature.
## Version information
Looks like there's now another report of this on the forums:
Same issue I experience. I have to add a "Trial" subscription to prevent this dialog from displaying.
Hotfix candidate 3.6-22834 against Xamarin 184.108.40.206 has been verified by QA and fixes this issue. This bug is being marked as verified.