[Bug]: OFX date parsing fails with newline and/or whitespace #2070

Closed
opened 2026-02-28 20:02:32 -06:00 by GiteaMirror · 6 comments
Owner

Originally created by @Sarke on GitHub (Apr 25, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Failed to parse date in OFX (downloaded from RBC Bank (US)), it shows up as 1899 something.

How can we reproduce the issue?

This is an example of the offending OFX (whitespace preserved):

							<STMTTRN>
									<TRNTYPE>
												CREDIT</TRNTYPE>
											<DTPOSTED>
												20231206211013</DTPOSTED>
											<TRNAMT>
												693.25</TRNAMT>
										<FITID>11866</FITID>
									<MEMO>Mailed in Deposit</MEMO>
										</STMTTRN>

I believe it is the line-break and/or whitespace before the date that is causing the issue.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox

Operating System

Linux

Originally created by @Sarke on GitHub (Apr 25, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? Failed to parse date in OFX (downloaded from RBC Bank (US)), it shows up as 1899 something. ### How can we reproduce the issue? This is an example of the offending OFX (whitespace preserved): ```xml <STMTTRN> <TRNTYPE> CREDIT</TRNTYPE> <DTPOSTED> 20231206211013</DTPOSTED> <TRNAMT> 693.25</TRNAMT> <FITID>11866</FITID> <MEMO>Mailed in Deposit</MEMO> </STMTTRN> ``` I believe it is the line-break and/or whitespace before the date that is causing the issue. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Firefox ### Operating System Linux
GiteaMirror added the bug label 2026-02-28 20:02:32 -06:00
Author
Owner

@MatissJanis commented on GitHub (Apr 25, 2025):

👋 Would you mind providing a full ofx file that we can use to reproduce the issue? Thanks!

@MatissJanis commented on GitHub (Apr 25, 2025): 👋 Would you mind providing a full ofx file that we can use to reproduce the issue? Thanks!
Author
Owner

@seannaesmb commented on GitHub (Apr 26, 2025):

I have attempted this action of "OFX Import", on a LONG transaction listing it failed, I tried a smaller time frame (30 days) and it was able to parse correctly and show imports. I did another from 1/1/25 to present day and it failed.

@seannaesmb commented on GitHub (Apr 26, 2025): I have attempted this action of "OFX Import", on a LONG transaction listing it failed, I tried a smaller time frame (30 days) and it was able to parse correctly and show imports. I did another from 1/1/25 to present day and it failed.
Author
Owner

@alecbakholdin commented on GitHub (Apr 26, 2025):

@seannaesmb how many transactions was your long transaction list? May be we can generate one of a similar size with dummy data and see if that reproduces the issue? I'm struggling to reproduce with the snippet provided in the report right now.

@alecbakholdin commented on GitHub (Apr 26, 2025): @seannaesmb how many transactions was your long transaction list? May be we can generate one of a similar size with dummy data and see if that reproduces the issue? I'm struggling to reproduce with the snippet provided in the report right now.
Author
Owner

@Sarke commented on GitHub (Apr 28, 2025):

@seannaesmb That is unrelated to this issue. Please create a new issue.

@Sarke commented on GitHub (Apr 28, 2025): @seannaesmb That is unrelated to this issue. Please create a new issue.
Author
Owner

@Sarke commented on GitHub (Apr 28, 2025):

👋 Would you mind providing a full ofx file that we can use to reproduce the issue? Thanks!

rbcbank-test.qfx.txt

@Sarke commented on GitHub (Apr 28, 2025): > 👋 Would you mind providing a full ofx file that we can use to reproduce the issue? Thanks! [rbcbank-test.qfx.txt](https://github.com/user-attachments/files/19934621/rbcbank-test.qfx.txt)
Author
Owner

@alecbakholdin commented on GitHub (May 1, 2025):

@Sarke you were right! Trimming the node values before importing solves this problem

@alecbakholdin commented on GitHub (May 1, 2025): @Sarke you were right! Trimming the node values before importing solves this problem
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2070