Details
-
Type:
Bug
-
Status: Closed
-
Priority:
High
-
Resolution: Fixed
-
Affects Version/s: Release 3.0.0
-
Fix Version/s: Release 3.0.2, Release 3.1.0, 2013 Sprint 02 JS, 2013 Sprint 02
-
Component/s: CLI
-
Environment:
Titanium Studio, build: 3.0.2.201301081713
-
Story Points:8
Description
While testing TISTUD-3120 I ran into the issue where log output in a for loop did not appear (see screenshot). I can only reproduce this issue in 3.0.2 not 3.1.0 or 3.0.1 using the attached app.js file in a standard titanium project.
This is a regression.
Steps to reproduce:
1. Open the Titanium project.
2. Run in Simulator.
Expected results:
All console output should be shown filtered based on settings.
Actual results:
Console output missing lines from the looped log calls.
Attachments
Issue Links
- is cloned from
-
TISTUD-3153 Log messages lost when logging commands are placed in a loop
-
- Closed
-
- is cloned into
-
TIMOB-16836 Parity: Android - Log messages lost when logging commands are placed in a loop
-
- Closed
-
- relates to
-
TIMOB-12364 CLI: iOS: build fails if using latest 3.0.2.v20130121114704 on iOS simulator
-
- Closed
-
-
TIMOB-12364 CLI: iOS: build fails if using latest 3.0.2.v20130121114704 on iOS simulator
-
- Closed
-
-
TISTUD-3120 iOS Simulator: console log level filter does not work
-
- Closed
-