Bug 451000

Summary: parse error when importing OFX file
Product: [Applications] kmymoney Reporter: M Both <both>
Component: importerAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: RESOLVED DUPLICATE    
Severity: critical CC: LibreStephen
Priority: NOR    
Version: 5.1.2   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description M Both 2022-03-01 11:46:12 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
When I try to import an .OFX transactions file into Version 5.1.2-a75e034b4, this is an example of the error message:
Unable to import 'C:/Users/both/Downloads/NatWest-May2021-20220214.ofx' using the OFX importer plugin. The plugin returned the following error:
Unable to parse file

STEPS TO REPRODUCE
1. download .OFX data file
2. import
3. get error

I tried removing the OFX Importer from configuration and then readding but it mdae no difference.

OBSERVED RESULT
I note that the same files can be imported into version 5.0.6 without difficulty (I have both KMyMoney versions installed on my laptop).  I sometimes get parse errors when I use  JSON / Javascript if there are certain characters (especially , ' and £) being imported so I use a regex in a PHP file to process these first.  Just a thought, probably nothing to do with the error but if the 

Even with that version, it doesn't alwaus get the anmes right and I have to manually correct it, but that is a minor issue.

EXPECTED RESULT
update transactions files

SOFTWARE/OS VERSIONS
Windows: 10 64bit


KDE Frameworks Version: Version 5.89.0
Qt Version: Version 5.15.2 (built against 5.15.2)

ADDITIONAL INFORMATION
Comment 1 Thomas Baumgart 2022-03-01 11:57:20 UTC
*** Bug 450999 has been marked as a duplicate of this bug. ***
Comment 2 Thomas Baumgart 2022-03-01 11:57:51 UTC

*** This bug has been marked as a duplicate of bug 450426 ***