Bug 22481 - XS 5.3 Build 439 apparently broke my licensing
Summary: XS 5.3 Build 439 apparently broke my licensing
Status: RESOLVED DUPLICATE of bug 22556
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: Activation ()
Version: 1.10.0
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Timothy Risi
URL:
Depends on:
Blocks:
 
Reported: 2014-08-28 16:20 UTC by troy-dawson
Modified: 2014-09-03 13:25 UTC (History)
6 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:
RESOLVED DUPLICATE of bug 22556

Description troy-dawson 2014-08-28 16:20:21 UTC
getting compile error that I need business license.

tried logging out & in but that didn't work

reloaded build 427 from the dmg cache and things are working again.
Comment 1 troy-dawson 2014-08-28 16:20:56 UTC
Should note that this is an Indie license and I'm trying to build a Unified Mac project.
Comment 2 troy-dawson 2014-08-30 16:53:32 UTC
Same with the 5.4 drop:

MMPTASK: error MM9008: Building from the command-line requires a Business license.


Xamarin Studio
Version 5.4 (build 178)
Installation UUID: 4b991e3f-5b17-407e-970d-153a6e5764e2
Runtime:
	Mono 3.8.0 ((no/62a857e)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 308000007

Apple Developer Tools
Xcode 6.0 (6256.16)
Build 6A280e

Xamarin.Mac
Version: 1.11.0.1 (Indie Edition)
Comment 3 Timothy Risi 2014-08-31 02:59:41 UTC
Hi Troy,

Are you having issues building from within Xamarin Studio, or only from the command line?
Comment 4 troy-dawson 2014-08-31 11:46:26 UTC
This is from within the IDE; with XS 5.4 I get this with a new Mac Unified project:

MMPTASK: error MM9008: Building from the command-line requires a Business license.
	Task "MmpTask" execution -- FAILED
	Done building target "_CompileToNative" in project 

(building a new MonoMac project in 4.3 succeeds)
Comment 5 troy-dawson 2014-08-31 11:47:30 UTC
^5.4 not 4.3 in my above
Comment 6 Rolf Bjarne Kvinge [MSFT] 2014-09-02 13:12:05 UTC
Are you on Yosemite or Mavericks?
Comment 7 Brendan Zagaeski (Xamarin Team, assistant) 2014-09-02 16:44:28 UTC
In case it might be helpful, I can reproduce this error using an Indie license.


## Version information

Xamarin Studio 5.3.0.435
Xamarin.Mac 1.10.0.9 (Indie Edition)
Mono 3.8.0 (no/62a857e)

OS X 10.9.4
Xcode 5.1 (5084), Build 5B130a



## Workaround

As noted in comment 0, downgrading to the earlier beta channel build of Xamarin Studio (5.3.0.427) also stops the error.

Downgrading Xamarin Studio to 5.2.1.1 (the current stable build) also stops the error.


For any other users who might run across this, If you'd like to try this workaround, you can get the individual Xamarin Studio 5.2.1.1 installer from:
https://store.xamarin.com/account/my/subscription/downloads

You might need to click the "View all versions" link to see the individual product drop-down menus. (See also http://forums.xamarin.com/discussion/10132/howto-install-older-versions-of-xamarin-software)
Comment 8 troy-dawson 2014-09-02 20:33:07 UTC
I am running 10.10 14A329f
Comment 9 Rolf Bjarne Kvinge [MSFT] 2014-09-03 04:04:02 UTC
Probably a dup of #22556
Comment 10 Rolf Bjarne Kvinge [MSFT] 2014-09-03 13:25:17 UTC

*** This bug has been marked as a duplicate of bug 22556 ***