[TIMOB-24529] iOS: "Cannot read property 'cyan' of undefined 0" when building project
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | n/a |
| Status | Reopened |
| Resolution | Unresolved |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | n/a |
| Labels | cb-tooling, iOS |
| Reporter | Mohammed AL-awadi |
| Assignee | Chris Barber |
| Created | 2015-01-11T16:45:23.000+0000 |
| Updated | 2020-01-30T21:59:54.000+0000 |
Hi, Please answer following questions: 1. Does this only happen the add module in project? 2. If yes, can you tell us which module does it happen to? 3. Does this happen only for one app or any app with the modules? 4. How did you build the project? Ti command or from studio? Regards, Shuo
Hi shuo, 1. this doesn't happen when adding module in project, it happen for any project including hello world default project regardless it has module or not . 2. i'm building the project using studio.
Hello, Please use the released CLI, not the daily build in order to find out if the CLI-dev is the source of the failing. Titanium Command-Line Interface, CLI version 3.4.1, npm uninstall titanium -g and then npm install -g titanium It should get 3.4.1 for you. Best Regards
Since I updated to 3.5.0-rc, even after rolling back.. I have this exact error as well. The strange thing is that when I use Studio I don't, but then it fails after starting the Simulator.
Hello, Is it still an issue for you? We did not reproduce this issue in our latest environment so far. So I recommend you to upgrade your Studio, SDK and CLI to the latest build then let us know if you get the error again. *Testing Environment:* Command-Line Interface, version 4.1.2, Ti SDK: 4.1.0.GA, iOS Simulator: 5,6(v8.4) Xcode: 6.4, Appcelerator Studio: 4.1.1 Thanks.
The related line is: https://github.com/appcelerator/titanium_mobile/blob/master/node_modules/node-appc/lib/timodule.js#L482
params.logger && params.logger.debug(__('Detected %s module: %s %s @ %s', platform, mod[ver].manifest.moduleid.cyan, ver, mod[ver].modulePath));moduleidin it. [~mohammedalawady] can you check that? [~morahman] even if this is a user error we can improve the above line by checking if the manifest is valid and if not, warn.