Bug 12124 - User is able to build and run iOS application with invalid license.
Summary: User is able to build and run iOS application with invalid license.
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 6.3.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2013-05-06 14:17 UTC by Saurabh
Modified: 2013-05-07 04:10 UTC (History)
3 users (show)

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:

Comment 1 PJ 2013-05-06 14:18:59 UTC
Is this a regression in iOS or in XS?
Comment 2 Saurabh 2013-05-06 14:42:05 UTC
An update to above issue:

Regression: Not a Regression.
This issue also exist with with XS, Mono3.0.11 and MT
This issue also exist with XS, Mono 2.10.12 and X.iOS
Comment 3 PJ 2013-05-06 14:52:27 UTC
I cant reproduce this.

The license file is ~/Library/MonoTouch/License.v2 - that might be the problem?

The one for MFA is slightly different, it's ~/Library/MonoAndroid/License

(the difference here is the .v2)

I am unable to reproduce the issue after running  touch ~/Library/MonoTouch/License.v2

After talking to Saurabh on skype, this was indeed the problem. The test case will be updated.
Comment 4 Nischal 2013-05-07 04:10:02 UTC
As per Comment#3 changing the status of this bug to Verified.