[AC-2815] codecs.py parse 0xE3 bug may be. BUILD FAILED occurred on 'Install to iOS Device'
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | n/a |
| Status | Closed |
| Resolution | Won't Fix |
| Resolution Date | 2012-08-11T16:10:20.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Titanium SDK & CLI |
| Labels | ios |
| Reporter | Tadashi Sugie |
| Assignee | Mauro Parra-Miranda |
| Created | 2012-05-21T19:08:56.000+0000 |
| Updated | 2016-03-08T07:47:44.000+0000 |
Description
app.js wrote following one line.
// としてTi.U.PICKER_TYPE_DATEを
Install to iOS Device , then BUILD FAILED occur.
---build.log---
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe3 in position 43: ordinal not in range(128)
Command /bin/sh failed with exit code 1
** BUILD FAILED **
---/build.log---
---app.js source code hex dump ---
[1036][sugie@mini-ssd:Resources]$od -cx app.js
0000000 / / と ** ** し ** ** て ** ** T i . U
2f2f e320 a881 81e3 e397 a681 6954 552e
0000020 . P I C K E R _ T Y P E _ D A T
502e 4349 454b 5f52 5954 4550 445f 5441
0000040 E を ** ** \n
e345 9282 000a
0000045
[1036][sugie@mini-ssd:Resources]$
---/app.js source code hex dump ---
There are some 'e3' codes.
May be codecs.py can not parse 'e3' code.
Attachments
| File | Date | Size |
|---|---|---|
| build.log | 2012-05-21T19:08:56.000+0000 | 115419 |
| TC-911_SDK2.0.1.GA2_ERROR.png | 2012-08-08T19:40:04.000+0000 | 216909 |
| TC-911_SDK2.0.2.GA_OK.png | 2012-08-08T19:40:04.000+0000 | 409135 |
| TC-911_SDK2.1.0.GA_OK.png | 2012-08-08T19:40:04.000+0000 | 410380 |
| TC-911_SDK2.1.1.GA_OK.png | 2012-08-08T19:40:04.000+0000 | 408928 |
Tadashi, I cannot reproduce this issue. Is it still an issue for you? Which Titanium SDK are you currently using?
I'm using SDK Version is 2.1.1.GA. I confirmed this bug. SDK 2.0.2 later not occurred this error.
Hi Tadashi, I've reproduced your issue while installing on device, my fault before. I have made some research and I found out that this is actually not a Titanium bug, but it's due to the following fact, also explained here http://docs.python.org/howto/unicode.html under the section 'Python 2.x’s Unicode Support' Basically all the argument of the unicode constructor should be 8-bit strings. In our case, ASCII encoding it's used for the conversion and what's happening is that a character greater than 127 is treated as an error. Thus, we cannot support this string character in the provided sample. Regards, Federico