[TIMOB-6438] iOS : TableView - When running QTS on an iOS device 5.0+, after finishing a test and navigating back to the main list of tests, one cannot run any other tests without terminating the app
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2012-02-27T16:08:58.000+0000 |
Affected Version/s | Release 1.8.0.1 |
Fix Version/s | Sprint 2012-04, Release 2.0.0 |
Components | iOS |
Labels | ios-jscore, qe-ios112911, regression |
Reporter | Michael Pettiford |
Assignee | Stephen Tramer |
Created | 2011-12-02T13:53:52.000+0000 |
Updated | 2012-03-19T10:12:24.000+0000 |
Description
Steps to reproduce:
Grab the QTS app from git@github.com:appcelerator/titanium_mobile_tests_internal.git
1. Launch the app on an iOS device running iOS 5+
2. Once the app is running, press any table view row (you don't have to run the test)
3. Navigate back to the main table view with all the tests
4. Press a new table view row
Expected result:
Able to run tests one after the other
Actual result:
Pressing the new table view row doesn't launch any new tests
Ran git bisect and found out this is broken since commit number "[cd2d7f7dbbd1efa1c098800d66b53777eaf2db1f] Merge pull request #269 from rseagraves/TIMOB-4523". Update to JSCore.
Vishal, can you please distribute your workaround for this to the QE team? This requires a JSCore update and must be postponed.
Bumping into sprint 49 so that we can perform some preemptive evaluation to find out which JSCore we're using, etc. before this is resolved (if we have time).
As a temporary workaround on ios device/simulator click on the first row (title:'Cross-platform') a few times before you start testing. This seems to magically solve the issue.
Scheduling for 1.9.0 timeframe as this is a JSCore bug. We will try and batch them together to get a single JSCore update for the next minor rev.
Reassigning to Thom as part of the post-1.8.2 pass where it will get evaluated to see if JSCore fixed up this nasty problem then.
Bumping for Thom to validate in S5 against a new JSCore.
Looks like the new JSCore fixes this.
Confirmed to be resolved by jscore update TIMOB-6292, putting in the appropriate sprint for resolution
Fixed by pull #1520.
Closing issue Tested with Ti Studio build 2.0.0.201203182248 Ti Mob SDK 2.0.0.v20120319003254 hash r60b6da4c OSX Lion 10.7.3 iPad 1 OS 5.1 Verified that the expected behavior is shown