Exception when launching in OSX Mountain Lion

[GoogleCodeExporter]

Launch the application in OSX and it crashes right away.

java -version
java version "1.7.0_05"
Java(TM) SE Runtime Environment (build 1.7.0_05-b06)
Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode)

Exception in thread "AWT-EventQueue-0" java.lang.IllegalArgumentException: 
URLDecoder: Illegal hex characters in escape (%) pattern - For input string: 
"&i"
    at java.net.URLDecoder.decode(URLDecoder.java:192)
    at fr.free.movierenamer.utils.Utils.unEscapeXML(Utils.java:402)
    at fr.free.movierenamer.parser.xml.MrRenamedMovie.startElement(MrRenamedMovie.java:66)
    at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:506)
    at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:182)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1302)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2715)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:607)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:835)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
    at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123)
    at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1210)
    at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:568)
    at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:302)
    at fr.free.movierenamer.parser.xml.XMLParser.parseXml(XMLParser.java:79)
    at fr.free.movierenamer.ui.MovieRenamer.loadRenamedMovie(MovieRenamer.java:250)
    at fr.free.movierenamer.ui.MovieRenamer.<init>(MovieRenamer.java:105)
    at fr.free.movierenamer.Main$1.run(Main.java:62)
    at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:701)
    at java.awt.EventQueue.access$000(EventQueue.java:102)
    at java.awt.EventQueue$3.run(EventQueue.java:662)
    at java.awt.EventQueue$3.run(EventQueue.java:660)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:671)
    at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:244)
    at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:163)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:147)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:139)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:97)

Original issue reported on code.google.com by Christopher.McNeil on 18 Nov 2012 at 6:33

[GoogleCodeExporter]

I think, i see what's happen, but unfortunately we work on next version which 
is re-write almost from scratch.

Meanwhile next version will be release, you can try to "solve" this problem by 
removing "renamed.xml" file which is in your HOME folder, something like that 
(i don't have MAC OS) :

/home/YOUR_USER/.Movie_Renamer/cache/renamed.xml

It's a hidden directory.

If the problem persist, just reply or send me a mail at 
contact@movie-renamer.fr and i will see what i can do , so that you could 
continue to use Movie Renamer.

Sorry for the inconvenience.

Original comment by nico.ma...@gmail.com on 18 Nov 2012 at 8:02

[GoogleCodeExporter]

Awesome, thanks for the fix and quick response!! I'm excited for the next 
version :)

Original comment by Christopher.McNeil on 18 Nov 2012 at 4:07