[TIMOB-2516] Android: common .js bad module errors (at least 2 weeks old, not seen in 1.4.2)
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Invalid |
Resolution Date | 2011-04-15T03:21:46.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Release 1.5.0 M05 |
Components | Android |
Labels | android, defect, regression |
Reporter | Thomas Huelbert |
Assignee | Don Thorp |
Created | 2011-04-15T03:21:46.000+0000 |
Updated | 2017-03-02T20:59:40.000+0000 |
Description
Titanium SDK version: 1.5.0 (12/06/10 08:42 4d92d40), device and sim
1.Platform > common js with logcat going
results:
D/TitaniumModule( 5647): (kroll$118) [34,1335484] Attempting to
include native module: echo
D/TitaniumModule( 5647): (kroll$118) [26,1335510] Attempting to
include native module: echo
D/TitaniumModule( 5647): (kroll$118) [22,1335532] Attempting to
include native module: bad_module
E/TitaniumModule( 5647): (kroll$118) [0,1335532] Error loading
module named: bad_module
full pastie: http://pastie.org/1353874">http://pastie.org/1353874
The bad_module error is expected, since it doesn't exist (the test is trying to make sure loading a bad module throws an exception, and when it catches it, the label shows that it passes)
Closed as invalid.