GNOME Bugzilla – Bug 572107
OFX import crashes (Windows)
Last modified: 2018-06-29 22:18:20 UTC
Steps to reproduce: Steps to reproduce: 1. On Windows Gnucash 2.2.8, create a new empty account system 2. Do File>Import>OFX of an OFX file containing the below: You get an immediate crash. Thanks, Patrick Stack trace: Other information: OFXHEADER:100 DATA: OFXSGML VERSION:102 SECURITY: NONE ENCODING: ISO-8859-1 CHARSET:1252 COMPRESSION: NONE OLDFILEUID: NONE NEWFILEUID: NONE <OFX> <SIGNONMSGSRSV2> <SONRS> <STATUS><CODE>0<SEVERITY>INFO</STATUS> <DTSERVER>20030421 <LANGUAGE>GER <COUNTRY>GER </SONRS> </SIGNONMSGSRSV2> <BANKMSGSRSV2> <STMTTRNRS> <TRNUID>20090215211215811 <STATUS><CODE>0<SEVERITY>INFO</STATUS> <STMTRS> <CURDEF>EUR <BANKACCTFROM> <BANKID>50050201 <ACCTID>1252000000 <ACCTTYPE2>checking </BANKACCTFROM> <BANKTRANLIST> <DTSTART>19700101 <DTEND>20030421 <STMTTRN> <TRNTYPE>CREDIT <DTPOSTED>20081230 <DTUSER>20081230 <TRNAMT>0.23 <FITID>2008-12-30 23:57:49.108476 <NAME>(0000000000/50050201): **Endsaldo** </STMTTRN> </BANKTRANLIST> </STMTRS> </STMTTRNRS> </BANKMSGSRSV2> </OFX>
Created attachment 128885 [details] OFX file which is crashing
Seems to happen with GnuCash 2.2.9 as well.
Ok, the crash is fixed by r17965 on trunk. Requesting for a backport. Patrick, thanks a lot for your report! I have always thought that OFX would be real XML data, so you might have better luck if you manually close the elements your forgot. I actually have not tried that. As written above, the crash should (probably) be fixed when GnuCash 2.2.10 or 2.3.x comes out.
(In reply to comment #3) > your forgot ^^^ bank
Hi Andreas, until 2.2.10 comes out is there a way for me to manually fix the file from my bank? Thanks, Patrick
Since there will be no 2.2.10, I'm going to resolve this with target milestone 2.3.0.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=572107. Please update any external references or bookmarks.