Date range error in main page
watertrainer opened this issue · comments
The exact error is
Exception: Invalid Response from AP: ("message":"Internal Firefly Exception: Epoch doesn't fit in a PHP integer""exception":"'DateRangeError"}
It appears in the first and fourth card. I don't have any transactions in February in firefly yet, could that be the source of the issue?
Hi, could you please enable and send me the debug logs please? In Settings, tap version, enable, refresh the main page, go back to settings and send log (afterwards disable).
What Firefly version are you using?
The newest one, just updated this morning to 6.1.9, that might be the problem, but doesn't look like any changes to the api were made.
Ok so I did some digging and it seems like the error is happening in this request, but as far as I can tell, the start and end dates are correct and shouldn't produce this error
waterfly-iii/lib/pages/home/main.dart
Line 628 in f60063b
This is what the debugger shows right before the request gets sent.
It looks like something is wrong in your database - see for example firefly-iii/firefly-iii#5842 & firefly-iii/firefly-iii#5179, where they ended up deleting the affected TX after figuring out which one it was.
Might this also affect you? Do all account overviews in the webinterface work? I tested out with the demo page with various combinations (date in the future, date now but no transactions, date in the past and no transactions etc.) but was never able to produce an error.
I only have three transaction in the timespan which gives an error (which was created with the app), and it looks to be fine in the web app, everything loads correctly there too.
Those are the transactions in question:
I trust you even without the Screenshots ;) Unfortunately there is nothing I can see wrong with the apps code, so it looks like a firefly issue (well, it definitely is, since the API call itself looks normal, and the demo page works fine). I'm not sure I can do anything to help you out there - might be best to report the error-throwing API call to JC5 in the FF3 issue tracker. Sorry about that :(