Error when trying to generate a csv-export file


#1

Hello,

since several days I have the following problem: Whenever I try to use the backup/export function, I am getting an error message “There was a problem exporting the readings. Please try again.”

Since I was able to use the function between the 5th and the 10th of February I am wondering why it is suddenly not working anymore.

My phone is a LG G5 (H850) with LineageOS (without Gapps) installed on it. Since everything was working at the beginning I am confused what could have caused this issues…

I tried already clearing the cache. I even reinstalled the app. However, unfortunately I am not able to get the export-function working again… Does anybody have an idea how to resolve this issue?

Thanks in Advance!


#2

Is there any chance you can get a copy of your console log to give us some clues as to what might be happening?


#3

Is there any tutorial which explains how to get a console log? Is it just stored in some folder on the internal storage (or sd card)?


#4

I think you might need to enable developer options on your phone and use the ‘take bug report’ option, as described here:

https://developer.android.com/studio/debug/dev-options


#5

I don’t know if this is the console log you were asking about, but here you have a copy. Please let me know if you are unable to find the root cause in the logs. I was resetting/clearing the logs right before I generated the export, for overview purposes. So in the case you are unable to find some information in the logs I could generate some new logs (for instance right from the start of the app?)

Thanks in Advance!

--------- beginning of main
02-16 13:12:03.196  1423  1607 D AudioService: Stream muted, skip playback
02-16 13:12:03.588  1423  1566 D sensors_hal_Ctx: poll:polldata:1, sensor:0, type:1, x:0.613556 y:4.434235 z:8.986237
02-16 13:12:03.589  1423  1566 D sensors_hal_Util: waitForResponse: timeout=0
02-16 13:12:03.628  1423  1566 D sensors_hal_Ctx: poll:polldata:1, sensor:0, type:1, x:0.790726 y:4.369583 z:8.746811
02-16 13:12:03.628  1423  1566 D sensors_hal_Util: waitForResponse: timeout=0
02-16 13:12:03.650  1423  1497 D sensors_hal_SMGR: processBufferingInd:report(on_change_sensor) eventtype 0
02-16 13:12:03.650  1423  1566 D sensors_hal_Ctx: poll:polldata:1, sensor:1, type:5, x:54.000000 y:0.000000 z:0.000000
02-16 13:12:03.650  1423  1566 D sensors_hal_Util: waitForResponse: timeout=0
02-16 13:12:03.667  1423  1566 D sensors_hal_Ctx: poll:polldata:1, sensor:0, type:1, x:0.819458 y:4.486893 z:8.358948
02-16 13:12:03.667  1423  1566 D sensors_hal_Util: waitForResponse: timeout=0
02-16 13:12:03.707  1423  1566 D sensors_hal_Ctx: poll:polldata:1, sensor:0, type:1, x:1.130707 y:4.300156 z:8.938354
02-16 13:12:03.707  1423  1566 D sensors_hal_Util: waitForResponse: timeout=0
02-16 13:12:04.244  1423  1607 D AudioService: Stream muted, skip playback
02-16 13:12:05.220  1423  1607 D AudioService: Stream muted, skip playback
02-16 13:12:05.220  3451  3451 I Glucosio: Storage permissions granted.
02-16 13:12:05.229  3451  3619 D Activity: onExportStarted(): you might want to track this event
02-16 13:12:05.233  3451  3619 I glucosio: Dir exists
02-16 13:12:05.238  3451  3619 W System.err: java.text.ParseException: Unparseable date: "Fri Feb 15 23:07:17 GMT+01:00 2019"
02-16 13:12:05.238  3451  3619 W System.err: 	at java.text.DateFormat.parse(DateFormat.java:358)
02-16 13:12:05.238  3451  3619 W System.err: 	at ux.d(Unknown Source)
02-16 13:12:05.238  3451  3619 W System.err: 	at vf.a(Unknown Source)
02-16 13:12:05.238  3451  3619 W System.err: 	at uo$1.a(Unknown Source)
02-16 13:12:05.238  3451  3619 W System.err: 	at uo$1.doInBackground(Unknown Source)
02-16 13:12:05.238  3451  3619 W System.err: 	at android.os.AsyncTask$2.call(AsyncTask.java:305)
02-16 13:12:05.238  3451  3619 W System.err: 	at java.util.concurrent.FutureTask.run(FutureTask.java:237)
02-16 13:12:05.238  3451  3619 W System.err: 	at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:243)
02-16 13:12:05.238  3451  3619 W System.err: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
02-16 13:12:05.238  3451  3619 W System.err: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
02-16 13:12:05.238  3451  3619 W System.err: 	at java.lang.Thread.run(Thread.java:761)
02-16 13:12:05.239  3451  3619 W System.err: java.lang.NullPointerException: Attempt to invoke virtual method 'long java.util.Date.getTime()' on a null object reference
02-16 13:12:05.239  3451  3619 W System.err: 	at java.util.Calendar.setTime(Calendar.java:1089)
02-16 13:12:05.239  3451  3619 W System.err: 	at java.text.SimpleDateFormat.format(SimpleDateFormat.java:936)
02-16 13:12:05.239  3451  3619 W System.err: 	at java.text.SimpleDateFormat.format(SimpleDateFormat.java:929)
02-16 13:12:05.239  3451  3619 W System.err: 	at java.text.DateFormat.format(DateFormat.java:337)
02-16 13:12:05.239  3451  3619 W System.err: 	at ux.d(Unknown Source)
02-16 13:12:05.239  3451  3619 W System.err: 	at vf.a(Unknown Source)
02-16 13:12:05.239  3451  3619 W System.err: 	at uo$1.a(Unknown Source)
02-16 13:12:05.239  3451  3619 W System.err: 	at uo$1.doInBackground(Unknown Source)
02-16 13:12:05.239  3451  3619 W System.err: 	at android.os.AsyncTask$2.call(AsyncTask.java:305)
02-16 13:12:05.239  3451  3619 W System.err: 	at java.util.concurrent.FutureTask.run(FutureTask.java:237)
02-16 13:12:05.239  3451  3619 W System.err: 	at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:243)
02-16 13:12:05.239  3451  3619 W System.err: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
02-16 13:12:05.239  3451  3619 W System.err: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
02-16 13:12:05.239  3451  3619 W System.err: 	at java.lang.Thread.run(Thread.java:761)
02-16 13:12:05.255  3451  3451 E Activity: onExportError(): you might want to track this event

#6

Well that looks interesting - I think it might indicate that there is a problem handling the date format you have chosen for your phone settings (or maybe it is just a bug handling date formats more generally). It might be worth setting your phone locale/date formats to something else and trying again. Definitely a bug though - it shouldn’t crash or fail in this case, obviously, but sadly it does


#7

Is it planned to fix this bug in the future? Since I am putting a lot of data also in the comment field (comma separated) etc., I would like to use the data from the csv-file for my own diagrams and research…

What I have tried now already is changing the time from the 24-hour form to the 12-hour AM/PM clock. However it did not change anything at all… Export function is still not working :frowning:

It would really be great if this could be fixed.


#8

We will try to get this fixed but there aren’t many Android developers helping us right now, so I can’t give you a very accurate time frame, I’m sorry about that