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.
Steps to reproduce this issue:
[Condition: License should be Priority on disk]
1. Open or create android application.
2. Go to project option->Android build.
3. Select option 'Embed assemblies in native code'.
4. Now Quite xamarin Studio
5. Make license as Invalid on disk using touch command
6. Open X.S again and open same project.
7. Check/uncheck option 'Embed assemblies in native code' , Observe that nothing happens.
8. Build the project when option is checked.
Actual result: When user build the application, it redirects to component page and if user go back to IDE, Trigger shows that "You must renew your license to continue using Business Edition; otherwise, you may use Starter Edition"
Even when option is unchecked and user build the application same behavior appears.
Expected Result: When license is invalid on disk, and user build the application after selecting option 'Embed assemblies in native code', trigger popup should appear to prompt for 'Purchase a license' and login with existing account even on trigger popup it should display as "You must renew your license to continue using Enterprise Edition".
X.S 4.0.9(build 15)
An update to the issue is:
This is build output for the same: https://gist.github.com/anonymous/b2a102a855418d061263
The behavior here from spec, the workflow images, is that there's a difference if you're logged in and if you're not. It looks like the behavior you're reporting is the 'correct' behavior for this scenario:
User is not logged into an account in Xamarin Studio
User is logged into an account on the Web that does not have an active subscription
User has an invalid license on disk
User triggers INVALID workflow
So yeah, you are not logged in, so you get automatically thrown to the LOGIN workflow.
The LOGIN workflow sees that you're already logged in, so throws you back to the IDE
Your website account doesn't have the right account type, so after LOGIN you don't have the right keys, so that check fails, giving you the dialog titled 'Xamarin Studio did not find a current *Xamarin Android* license for your account", the INVALID main dialog.
So I'm not sure if we can make this any better right now, but please review my description here and let me know if anything else seems amiss with my assessment (specifically related to the additional conditions that you did not specify one way or another, the account status and log-in status on the web and in the IDE)
Also, this behavior should not be affected in any way by the Embed assemblies option, except if the condition 'User is logged into an account on the Web that does not have an active subscription' would be affected.
Today I have checked this issue with following builds:
X.S 4.0.9(build 15)
And we have checked following scenario hare:
1. When user is logged in to Web with account which does not have paid account
then it redirects to IDE and shows two options 'Purchase a license and use starter.
2. When user is logged into web with account which have paid account (Business, Indie) then it redirects to IDE and shows two options Purchase a license and Start a trial
3. When user is logged into IDE with paid account (Business, Indie) then it activate with Business/Indie and then shows two options Purchase a license and Start a trial
Hence closing this issue
*** Bug 12737 has been marked as a duplicate of this bug. ***