[TIMOB-11617] iOS: Ti.API: some console logging calls with array args do not print array to console
GitHub Issue | n/a |
---|---|
Type | Sub-task |
Priority | High |
Status | Closed |
Resolution | Invalid |
Resolution Date | 2012-11-01T20:52:58.000+0000 |
Affected Version/s | Release 2.1.3, Release 3.0.0 |
Fix Version/s | n/a |
Components | iOS |
Labels | parity, qe-ios100112 |
Reporter | Dustin Hyde |
Assignee | Ingo Muschenetz |
Created | 2012-10-31T00:06:24.000+0000 |
Updated | 2014-06-19T12:43:21.000+0000 |
Description
Some console logging calls with array args do not print array to console.
The cases are:
Ti.API.log('freeform', ['arg0', 'arg1'])
and
Ti.API.timestamp(['arg0', 'arg1'])
This does not occur in MobileWeb or Android. This is a parity issue.
This does not occur to other array printing calls in iOS. This is an internal inconsistency.
Steps to Reproduce:
1. Run code:
Ti.API.log('log', ['Ti.API.log.0', 'Ti.API.log.1']);
Ti.API.timestamp(['Ti.API.timestamp.0', 'Ti.API.timestamp.1']);
Actual Result:
[LOG] (
[TIMESTAMP] 373334748.160333 (
Expected Result:
[LOG] ( arg0, arg1 )
[TIMESTAMP] 373334748.160333 ( arg0, arg1 )
Tested with TiSDK 2.1.3 GA, 2.1.4 current build(e5cb5e62e9), 3.1.0 (master) build(99f510f) Xcode 4.5 , iOS 6.0, TiStudio build: 3.0.1.201210291936
Actual Result from the console
[LOG] ( "Ti.API.log.0", "Ti.API.log.1" ) [TIMESTAMP] 373403137.711285 ( "Ti.API.timestamp.0", "Ti.API.timestamp.1" ) Marking ticket as invalid. log and timestamp statements seems to printing out messages as it should.Invalidating the ticket
You think this is a Studio issue?
@Dustin console output in my comment is from Studio. I don't see any issue.
That's odd. I'm seeing the issue. OS: Mountain Lion 10.8.2 Hardware: MacBook Pro Retina SDK: 2.1.3.GA Studio: 2.1.2, 3.0.0.201210291448, 3.0.1.201210302321 CLI disabled. iPhone Simulator 6.0 Xcode 4.5.1
I don't see this on device, but I do see it on simulator (iPhone Simulator 5.0, 5.1, 6.0). iPhone 5.0.1 Xcode 4.5.2 Console:
Studio is going to rule this ticket out.
This is a studio issue, see clone for details. This should be closed as invalid.