[TIMOB-15800] Ubuntu: Found Missing Modules error on launching any default Mobile app
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Critical |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2013-11-25T23:55:48.000+0000 |
| Affected Version/s | Release 3.2.0 |
| Fix Version/s | 2013 Sprint 24, 2013 Sprint 24 Core, Release 3.2.0, Release 3.3.0 |
| Components | CLI |
| Labels | module_build, qe-3.2.0, qe-closed-3.2.0, qe-testadded, ti, ubuntu |
| Reporter | Shreya Chowbey |
| Assignee | Chris Barber |
| Created | 2013-11-19T09:11:01.000+0000 |
| Updated | 2014-07-31T18:30:22.000+0000 |
Description
Steps Followed:
1. Create a default mobile app. 2. Launch the app on android device/emulator. Actual Result: Build fails and 'Modules could not be found' error displayed in Console log file. Please refer the attached log and console log file for further reference.Workaround
We manually added the required modules folders from mobile SDK location into our Studio WorkSpace in the respective project's module folder.Attachments
| File | Date | Size |
|---|---|---|
| Missing Modules - console log file | 2013-11-19T09:11:02.000+0000 | 1329 |
| Missing Modules - log file | 2013-11-19T09:11:02.000+0000 | 3551 |
Anyways, I can confirm I saw the same thing. I have the com.appcelerator.apm module in my ~/.titanium/modules/android folder, and the ti.cloud in ~/.titanium/modules/commonjs. When trying to run the app on Android emulator, I get the same error. I would assume that the CLI/platform would pick up the modules from their global locations.
The workaround Shreya stated, of copying the modules from the global location into the project's modules folders does fix the issue. So I'm at a loss as to whose bug this actually is. Here's what I see: * The app has the com.soasta.touchtest module installed into the app's modules/android folder. * The com.appcelerator.apm and ti.cloud modules aren't installed in the app itself, but are available in the global modules locations. * So I think the first issue is that the platform/CLI isn't picking up the modules from the global path properly. * The second possible issue is whether Studio should be copying/installing those two modules into 360 apps' modules folders like we do for com.soasta.touchtest.
Could you please reproduce the issue and attach the CLI log output with TRACE level output. Without TRACE level debug info, I can't see exactly what modules are being detected. TRACE log level will show all modules that are found. Also, please put the TRACE output in a .txt file so I can view it in a browser.
[~schowbey], [~emerriman] Can you please provide a copy of the CLI output?
Given the existence of a workaround, downgrading from blocker.
Pull request: https://github.com/appcelerator/titanium_mobile/pull/5023
Verified fixed on: Ubuntu 12.04 LTS Titanium Studio, build: 3.2.0.201311252022 Titanium SDK, build: 3.2.0.v20131126111643 CLI: 3.2.0-alpha3 Alloy: 1.3.0-alpha6 "ti module" displays all modules correctly. Created an Android application and attached all installed modules to the project. Ran the project on simulator and all modules were found successfully. Closing