Licensing a standard library project

Posted by: kp on 7 October 2020, 8:19 pm EST

    • Post Options:
    • Link

    Posted 7 October 2020, 8:19 pm EST - Updated 30 September 2022, 12:21 am EST

    I have an issue figuring out how to license a standard library project, while I have a working standalone IOS project without issues.

    For now im just testing the IOS part but im getting a “failed to generate license for component studio for Xamarin Details: no license” error.

    I have an app key created from the namespace of the project, placed in a “license file” as a constant string.

    the code I have in the Xamarin app.xaml.cs class is in the first image and the code I have for the appdelegate.cs class of iOS is in the second image.

    This should follow the walkthrough from the licensing page on the website:

    Could I get a pointer on what im missing?

    The packages I use are also in images 3 for the forms part and a bunch on the IOS part, partly because it added both the IOS and Forms variants when I told it to add the IOS libraries.

  • Posted 12 October 2020, 1:53 am EST

    Hi KP,

    =>“failed to generate license for component studio for Xamarin Details: no license”

    You are getting an error while generating the License Key for a Xamarin application, can you please confirm how you generated the key using in the “License file” of your application?


  • Posted 12 October 2020, 7:29 pm EST

    I generate a key by copy pasting the namespace into the “create apply” field on my account here(same as I did for my IOS only app) and then I copy the key to a file named license as a constant string. Then I use the above c1.ios.licensemanager.key = the key from the license file(remember it is just a file containing a constant not an actual generated license file". I do the same for the Xamarin forms part of the project except the license manager is the forms one.

    In my iOS only app I just have the key copied into the license manager, since it is only used once.

  • Posted 14 October 2020, 1:13 am EST

    Hi KP

    Can you please try using the GrapeCity License Manager for licensing your project. For referece please have a look at the below documentaion link

    Please let me know if you need any other help.


  • Posted 17 March 2021, 12:38 am EST

    It says in your link, that the extension is not out for Mac, I go it working by fidling around with the bin and obj folders in the project and then restoring, it sometimes fixes the problem, but it returns whenever I update the NuGet files.

    The page for the extension offers a solution through terminal by opening gclm (in visual studio terminal) but I also get a response “command not found” on gclm. Im going to keep trying the bin/obj folder deletion trick, but I’d very much like a solution that is more reliable on Mac.

    PS: I don’t think I marked this as the answer back when it was posted, I clicked it again today to see if I can unmark it as answer, specifically for my situation since I would think that is the perfect answer if I was using windows.

    Edit: i noticed my key was outdated and my new one uses the new system, which seems to be an entirely different issue. I will look around for help on that otherwise I will make a support ticket.

  • Posted 18 March 2021, 1:34 am EST

    Hi KP

    Can you please share a small sample replicating the issue? also if possible please share the screenshot of the error you are getting from the Visual Studio terminal.


Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels