Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-2823] Cannot use '&' for Description, Publisher or Copyright (in tiapp.xml)

GitHub Issuen/a
TypeBug
PriorityTrivial
StatusClosed
ResolutionDuplicate
Resolution Date2011-04-15T03:30:29.000+0000
Affected Version/sn/a
Fix Version/sn/a
ComponentsiOS
Labels1.5.x, 1.6, bug
ReporterAlan Leard
AssigneeBlain Hamon
Created2011-04-15T03:30:28.000+0000
Updated2017-03-22T22:21:04.000+0000

Description

If you use a '&' symbol in the Description, Publisher or Copyright fields of an app, the app will not run. This is the error generated:

Traceback (most recent call last):
File "/Users/alanleard/Library/Application Support/Titanium/mobilesdk/osx/1.6.0/iphone/builder.py", line 1269, in <module>
main(sys.argv)
File "/Users/alanleard/Library/Application Support/Titanium/mobilesdk/osx/1.6.0/iphone/builder.py", line 378, in main
ti = TiAppXML(tiapp_xml)
File "/Users/alanleard/Library/Application Support/Titanium/mobilesdk/osx/1.6.0/iphone/../tiapp.py", line 50, in __init__
self.dom = parseString(data.read().encode('utf-8'))
File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xml/dom/minidom.py", line 1928, in parseString
return expatbuilder.parseString(string)
File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xml/dom/expatbuilder.py", line 940, in parseString
return builder.parseString(string)
File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xml/dom/expatbuilder.py", line 223, in parseString
parser.Parse(string, True)
xml.parsers.expat.ExpatError: not well-formed (invalid token): line 8, column 31

Comments

  1. Alan Leard 2011-04-15

    App name also does not work with '&'

  2. Stephen Tramer 2011-04-15

    Duplicate of #717.

  3. AvtarSingh Suchariya 2013-07-17

    The same issue I was facing and resolved. The problem was I added Projct > i18n > en > string.xml file and one of the string contains & sign. I removed and the project was running smoothly.
  4. Lee Morris 2017-03-22

    Closing ticket as duplicate and links to the related ticket have been provided above.

JSON Source