0
Under review

Problems when importing CSVs

Bernhard Kirchen 12 years ago updated by Adrian 12 years ago 2
Hi!

I have a bunch of old fueling data which I wanted to import into the app. Doing so I stumbled over a bunch of problems:
  • when successfully importing a csv, the app reports a wrong number of imported lines, because the header does not contain valid data and hence ot should not contribute to the total number of data sets imported.
  • when importing a csv, the app seems non-responsive. hence, when importing a large csv (690 lines in my test), android asks for the app to be killed because it is non-responsive. AFAIK one should start a new thread for the import while the main app thread just waits for the completion of the spawned thread (I guess you already did that for the stats, when the app needs some time to calculate all the stuff?)
  • the app crashes when importing a csv with semicolon as column devider (instead of comma)
  • the app crashes when importing a csv with odometer value using decimal point
  • the app crashes when importing a csv that leaves out empty columns (meaning a csv with 5 columns (the first five in fuelio format), but the others left out, i.e. lines like "2005-12-15,108898,38.54,1,0.00" makes the app crash when imported)
  • the app crashes when looking at mileage log for a car that has been successfully imported by a csv which has one or more entries with missing total price of the filling (although it is described as "optional" in the csv header). 0 (Zero) for the total price will do.
So long,
Bernhard  
Thanks for your reports. I know, importing CSV is buggy. There is no sample format and I know that users have problem with it.

You could send me your csv and I will convert it to Fuelio format. 
I know I should add thread. Dropbox import has thread while importing CSV. Standard import will also be fix.

690 lines, big file. Fuelio doesn't have date/time limit at the moment. Now you could try to split your file (for example) per year ex. Car 2010, Car 2011 for better perfomance. 

In most cases CSV import crashes if you have wrong CSV format. I need to add some more exceptions (I've already did it in my local version of app).
Answer
Under review
> You could send me your csv and I will convert it to Fuelio format. 
thanks, but I'm done now. if I gave up then I wouldn't have identified the listed problems ;p

>
Now you could try to split your file (for example) per year ex. Car 2010, Car 2011 for better perfomance.
It's okay if you wait, since the app is finished at some point. it's not like the import fails.

>
I need to add some more exceptions
that's what I was going for. I though it might be helpful to have a list of problems ready. maybe problems you, as the developer, do not see.