GitHub Issue | n/a |
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2012-07-21T22:37:27.000+0000 |
Affected Version/s | Release 2.0.2 |
Fix Version/s | Release 2.0.2, Release 2.1.0, Sprint 2012-11 API |
Components | Android |
Labels | api, qe-and051412 |
Reporter | Natalie Huynh |
Assignee | Neeraj Gupta |
Created | 2012-05-23T09:49:46.000+0000 |
Updated | 2012-08-14T10:21:04.000+0000 |
This is a regression, last working on 2.0.1GA2
Steps to Reproduce:
1. Launch KS > Platform > XHR > XML Properties (Wait for loading to complete)
Actual:
Returns unexpected values (See image)
Expected:
Should not have those values
PR 2259 fixes this on master
https://github.com/appcelerator/titanium_mobile/pull/2263 is pending for backporting to 2_0_X.
Tested with 2.0.2.v20120524124938 on Kindle Fire
Reopening bug because this bug occurs on: Titanium Studio, build: 2.1.1.201207161421 Titanium SDK version: 2.1.1.v20120718121609 Device: DROID3 (2.3.4) This is regression, doesn’t occur on 2.1.0. Screenshot is attached.
Tested on: Titanium Studio, build: 2.1.1.201207161421 Titanium SDK, build: 2.1.1.v20120718121609 Device: iPad 5.1 Comment: Text response time is 1.3
The "expected" behavior for this test isn't very clear. iOS seems to spew the same garbage for the responseText property. This is due to the response data being a PDF document (binary data).
Closing this since the behavior seen in 2.1.1 is correct. We see the PDF data now since we fallback ISO-8859-1 decoding which will handle pretty much any thing we throw at it. This is a fix in both iOS and Android. Both platforms exhibit this behavior now.
changing to "won't fix" based on the comment the behavior is as expected.
Closing bug based on the previous comments.