Bug 13032 - Use is unable to activate its Indie license for iOS on second machine.
Summary: Use is unable to activate its Indie license for iOS on second machine.
Status: VERIFIED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Activation ()
Version: 4.0.9
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: 4.0.10 (for async)
Assignee: Mikayla Hutchinson [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2013-07-03 08:36 UTC by Saurabh
Modified: 2013-07-10 15:27 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
VERIFIED FIXED

Description Saurabh 2013-07-03 08:36:12 UTC
Condition: 
User is login in IDE
Use has Indie license
No license is activated(no license on the disk)

User is unable to activate the Indie License on second(more than one) machine using the same credentials.


However there is a workaround for that:

User is not login in IDE. User triggers(like by adding restricted reference OR by clicking Project-> Profile-Mono) and user select 'Login with a Xamarin Account' option and login with an account having Indie license then Indie license is activated on the machine. 

Environment info:
Mono 3.0.12
XS 4.0.9(Build 12)
X.iOS 6.3.7.150

Note: For Xamarin.Amdroid, user can activate its Indie license by changing build action of any .cs file to AndroidJavaSourse, AndroidJavaLibrary or AndroidNativeLibrary.
Comment 1 PJ 2013-07-09 19:22:51 UTC
Heyo Saurabh, I'm not sure I'm clear here on the expected behavior vs the actual behavior.

If you are in the state described above, you should be automatically updated when you perform a restricted action.

I think this is the part you say is failing. Does this sound right?:

Conditions:
User is logged into the IDE with an account that has an active Indie subscription
User does not have a license on disk

Steps:

1) Open a Xamarin.iOS project
2) Use a pricing restricted feature that is usable by Indie (LinkWith, build with a large app size)

Expected behavior:

User should be automatically activated with the second activation on the Indie license

Actual behavior:

User is prompted with a workflow dialog and asked to Login again.




If that's an accurate report, then this is likely an issue with Xamarin Studio. Moving to that product, but please provide a followup ASAP so we can get to the bottom of this issue and get it to the right developer with time to spare before the release.

It's possible that you're only trying this with features that require business. For instance, using Profile-Mono requires the business edition, so if you try to use it with Indie it will prompt you to UPGRADE.  If this is the case, then the bug will be invalid.
Comment 2 Saurabh 2013-07-10 15:26:57 UTC
Conditions:
User is logged into the IDE with an account that has an active Indie subscription
User does not have a license on disk

Steps:

1) Open a Xamarin.iOS project
2) Use a pricing restricted feature that is usable by Indie (LinkWith, build
with a large app size)


Here, I have tried this with MWC iOS application and on building this sample(large size sample) Indie license activates on the machine.

Now, I am able to activate INDIE license on second machine with restricted feature (LinkWith, build with a large app size).

It is working same as expected behavior in comment 1

Hence, closing this issue.