Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-9138] Tooling: Unlicensed module error on existing projects

GitHub Issuen/a
TypeBug
PriorityHigh
StatusClosed
ResolutionInvalid
Resolution Date2012-05-22T17:08:24.000+0000
Affected Version/sRelease 2.0.1
Fix Version/sn/a
ComponentsTooling
LabelsSupportTeam, core
ReporterJunaid Younus
AssigneeAllen Yeung
Created2012-05-15T10:43:32.000+0000
Updated2017-03-09T23:28:25.000+0000

Description

When a user purchases a module from the marketplace and tries to use it with an existing project, it doesn't work and shows the 'unlicensed module error' screen. It works fine if you create a new project and add the module to it. A workaround is to create a new project and copy/paste the existing resource files into the new project, however this is not acceptable and shouldn't be happening.

Comments

  1. Junaid Younus 2012-05-15

    In this case, the client purchased the module called 'Cryptor' (3rd party) from the marketplace and it shows up the 'unlicensed module error' on existing projects. (Link to module: https://marketplace.appcelerator.com/apps/2479?1062962271 ) This isn't just related to a specific module, this is for all modules, other customers get the same problem (no matter if 3rd party module or not).
  2. Junaid Younus 2012-05-15

    To reproduce this issue: 1. Purchase any NEW module that you haven't already bought before (try it with a free 3rd party module). 2. Download it. 3. Add it to any EXISTING project and try to run the app inside the iOS simulator. 4. You should see the 'unlicensed module error' message appear. Workaround: 1. Create a new project. 2. Add the module to the new project 3. Run it in the iOS simulator 4. It will work fine, without any issues. I can't attach a sample project, because you have to manually purchase a module with the same account you use to log into TiStudio. Let me know if you have any questions.
  3. Neeraj Gupta 2012-05-15

    Junaid - we need the environment information for this ticket.
  4. Junaid Younus 2012-05-15

    Added environment details, however this should be platform independent and should be reproducible on any host OS. Let me know if there is anything else you need.
  5. Ian Howarth 2012-05-22

    There are a few scenarios that cause this error; 1. The project wasn't cleaned and the verification is cached as unlicensed 2. The marketplace hasn't assigned the product correctly 3. The user is running Studio without internet access Studio seems to play no part in this problem. I am marking the ticket as invalid and will re-open if I ever find an issue.
  6. Lee Morris 2017-03-09

    Closing ticket as invalid.

JSON Source