[TIMOB-8194] Android: Ti.UI.TableViewRow doesn't continuously update Ti.UI.ImageView objects inside of it
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Cannot Reproduce |
Resolution Date | 2013-05-21T11:46:37.000+0000 |
Affected Version/s | Release 1.8.2, Release 2.0.1, Release 3.1.0 |
Fix Version/s | 2013 Sprint 11 |
Components | Android |
Labels | exalture, parity, triage |
Reporter | Junaid Younus |
Assignee | Shameer Jan |
Created | 2012-03-22T13:06:59.000+0000 |
Updated | 2017-03-21T22:20:50.000+0000 |
Description
*Code*
.zip file attached with this ticket, which includes some images to reproduce this issue.
*Expected behavior*
When you tap on the row, it should update the image view with the correct image, continuously.
*Actual behavior*
On Android, it only seems to switch images once, and then never again.
*Notes*
-Only tested on an Android device and iOS simulator.
-On the iOS simulator, it seems to work perfectly fine.
-Only tested on 1.8.2.
-HD ticket: http://support-admin.appcelerator.com/display/APP-786776
Attachments
File | Date | Size |
---|---|---|
TableViewImageBug.zip | 2012-03-22T13:06:59.000+0000 | 3675017 |
Tested with 2.0.1GA2 on a Samsung Galaxy S2, issue still reproducible.
Guys - this is still happening in the 3.x codebase. Is there any way this can get prioritized to be fixed? It's pretty huge bug that's been ignored for a long time, considering it was first reported here in July 2011 http://support.appcelerator.com/tickets/APP-786776/report.
Issue reproduces with Titanium Studio, build: 3.0.1.201212181159 Titanium SDK version: 3.1.0 (03/11/13 15:43 0c88429) but works fine with Titanium Studio, build: 3.0.1.201212181159 Titanium SDK version: 3.0.2 (02/07/13 16:46 a4def81) Tested on Device: Samsung galaxy s duos Android version: 4.0.4 jithinpv
The issue cannot reproduce with the release master 3.2.0 Tested with: Titanium Studio, build: 3.0.1.201212181159 Titanium SDK version: 3.2.0 Tested on Device: Samsung galaxy s duos Android version: 4.0.4
Closing ticket as the issue cannot be reproduced and due to the above comments.