Consistently receiving error on save after upgrade to version 5.0

[effjay]

I love your software.  Unfortunately, the latest version has rendered the application pretty much unuseable. Perhaps it is something I am doing, but i'm using the application the same way I have for the past few months.  I'll create an entry and then go to add a stop time and attempt to save the time entry.  I receive an error that the entry cannot be saved.  The only way I have found to get rid of this error is to re-install the application.  This works for a time, but I then start receiving the error again.

The exact verbiage of the error message is: "Could not store Entry.  An error occured while storing this entry."

[effjay]

I just wanted to add that I did see the issue you were having with the expenses and it looks to be the same, however rebooting my device does not help.

[Adam]

Hi effjay,

We have had a few reports of this on the Time Entries now and for some the reboot hasn't worked and did require doing a Backup, then deleting the app, re-download it and the a Restore of the data.  Are you saying that you did that and still have a problem?  We think there is something odd going on with the way the update is happening from Apple, but if you have done that and are still having problems this is the first we've heard of that.  Please let us know?

[effjay]

That is what I'm saying.  When I couldn't save the entry I made a back up, my last one was from a while ago (naughty me), re-installed the application and restored the back up I just made.  I could try restoring from an older back up I suppose.  I record this information into a company approved system, the more detailed version is just for me.  Let me know if you think the recent back up could be the reason the problem has not resolved.

Thank you!

[Adam]

No, it's not the database file or the data within it.  For example the people having this problem can do a full good backup, delete the app, then re-download and restore the same database file and it seems to be working.  You are the first who has said that this problem has come back.

If you are willing, we'd like to get you setup with a beta version that will have a more verbose error message that will hopefully help us track down what is causing this.  We have not been able to replicate the issue here, but if you have then perhaps you can help us get this figured out.  If you want to do this please write us at support @ on-core dot com.