New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash when exporting transactions on 1.4.3 #223
Comments
Cannot reproduce this. However, I can see the problem in the code, and made a quick fix. I'm also very interested in the stack trace printed before this crash, to see why the export failed. Can you find it? |
Easy to reproduce for me, I just have to try an export ;) It seemed to be the root cause of the export crash to me, but here's the handmade copy of the trace: RuntimeException Actually looking at the code, there's nothing to fix because The problem seems to come from the above line, 110, That's how I understand it. But I can't get more information then the stacktrace provided above. |
It will indeed be difficult to find out why the export failed as the exception message is null in the first place. I've sometimes had issues like this which were specific to particular Android builds and not reproducible for anyone else. We need a deeper logging solution to catch this kinds of singular events. The fix which @fefe982 has added will prevent the whole app from crashing, but still not fix why your QIF is not generated. From what version did you notice that you couldn't generate QIF anymore? |
Right, e.getMessage() CAN be null, so it should tested beforehand. I guess it was from the last version I updated to, so I guess 1.4.3. I've got this Syslog app that allows me to send all the logs of my phone. I'll have a look quickly. |
Problem seems to be related to my MI UI version:
I guess |
This looks like the stack trace in #191 . Did you delete all transactions and keep the opening balance before you export? |
sounds like it yes, I remember I've tried that: I've enabled "keep the opening balance" but not delete all transaction. PS: It crashes the same with "Save accounts opening balances" disabled. |
null is returned trying to get the currency for the split's account, in |
It's triggered by What are these PS: It's apparently an i18n framework. I remember I've messed up with the currency of an account for convenience (switched back and force to Double Entry, then later on changed an account currency): it produced a bug once, but has been ok since. Could be related. |
I concur! On Mon, Sep 22, 2014 at 11:24 AM, Yongxin Wang notifications@github.com
|
OK, can't make sense of this since I'm not familiar with Gnucash internals but can't wait for it to be fixed ;) |
Fix will be available in the next version maybe around October. Plan is to enter beta soon. Join here: https://plus.google.com/u/0/communities/104728406764752407046 |
I've updated to version 1.5.1, the export function still crashes, in a cleaner fashion though thanks to @fefe982's fix. |
Does it crash with the same stack trace like before (the currency issue)? |
It does not show a stacktrace anymore as it's become a caught exception. But the system logcat display the same stacktrace as before:
|
What currencies are you using? |
Mostly CNY and EUR. |
@nodje can this issue be closed? |
I've had to start form scratch and recreate all my accounts to get exports to work again. I guess I won't be able to reproduce this bug ever. |
Basically, the stacktrace is saying:
NullPointerException: println needs a message at android.util.Log.println_native(Native Method)
at android.util.Log.e(Log.java:231)
at org.gnucash.android.export.ExporterAsyncTask.doInBackground(ExportAsyncTask.java:113)
at org.gnucash.android.export.ExporterAsyncTask.doInBackground(ExportAsyncTask.java:48)
Sounds pretty straightforward looking at the trace but I wonder why nobody has reported the bug earlier. It's a totally blocking bug for anyone using this app with the Gnucash desktop.
Could it be my distribution? MI UI 5
The text was updated successfully, but these errors were encountered: