urgent!! app refuses to start!

[ghost]

this is the error i see in the log file: --------- beginning of crash 02-11 02:21:40.194 3775 3775 E AndroidRuntime: FATAL EXCEPTION: main 02-11 02:21:40.194 3775 3775 E AndroidRuntime: Process: com.oriondev.moneywallet, PID: 3775 02-11 02:21:40.194 3775 3775 E AndroidRuntime: java.lang.RuntimeException: Unable to create application com.oriondev.moneywallet.App: java.lang.RuntimeException: Cannot decode file from string: Expected literal value at character 0 of /storage/emulated/0 02-11 02:21:40.194 3775 3775 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6465) 02-11 02:21:40.194 3775 3775 E AndroidRuntime: at android.app.ActivityThread.access$1300(ActivityThread.java:219) 02-11 02:21:40.194 3775 3775 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1859) 02-11 02:21:40.194 3775 3775 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107) 02-11 02:21:40.194 3775 3775 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214) 02-11 02:21:40.194 3775 3775 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7356) 02-11 02:21:40.194 3775 3775 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method) 02-11 02:21:40.194 3775 3775 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491) 02-11 02:21:40.194 3775 3775 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940) 02-11 02:21:40.194 3775 3775 E AndroidRuntime: Caused by: java.lang.RuntimeException: Cannot decode file from string: Expected literal value at character 0 of /storage/emulated/0 02-11 02:21:40.194 3775 3775 E AndroidRuntime: at com.oriondev.moneywallet.model.SAFFile.<init>(SAFFile.java:47) 02-11 02:21:40.194 3775 3775 E AndroidRuntime: at com.oriondev.moneywallet.api.BackendServiceFactory.getFile(BackendServiceFactory.java:82) 02-11 02:21:40.194 3775 3775 E AndroidRuntime: at com.oriondev.moneywallet.broadcast.AutoBackupBroadcastReceiver.startBackgroundTask(AutoBackupBroadcastReceiver.java:105) 02-11 02:21:40.194 3775 3775 E AndroidRuntime: at com.oriondev.moneywallet.broadcast.AutoBackupBroadcastReceiver.scheduleAutoBackupTask(AutoBackupBroadcastReceiver.java:59) 02-11 02:21:40.194 3775 3775 E AndroidRuntime: at com.oriondev.moneywallet.App.initializeScheduledTimers(App.java:60) 02-11 02:21:40.194 3775 3775 E AndroidRuntime: at com.oriondev.moneywallet.App.onCreate(App.java:51) 02-11 02:21:40.194 3775 3775 E AndroidRuntime: at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1189) 02-11 02:21:40.194 3775 3775 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6460) 02-11 02:21:40.194 3775 3775 E AndroidRuntime: ... 8 more

i would strongly appreciate any help because i depend on this app for my finances......

[ghost]

i am suspecting that this error is caused by me enabling the scheduled backup. it has crashed before when i was trying to enable it. is there a way i can disable the automatic backup without opening the app?

[ghost]

i luckily created a recent backup, so i took the chance and deleted the app data. then i restored the backup and added the missing data. so problem is "solved", but the reason for the crash and errors still exists.

as far as i remember, fiddling with the scheduled backup setting caused a crash.

[marvinmai]

Same for me, this is really unfortunate, took me a long time to enter all values and don't have any backup yet! @AndreAle94 could please take a look at that issue?

[Anachron]

"Fix the error ASAP. Please!" Well what a nice tone you have to someone who spends his free time working on something he gets no money for. A little spoiled are we, no?

[Anachron]

Go away. Please! (Great, I found a way how to be polite.)

[junoslukan]

This has happened to me before, too, and I also suspect it had to do with the scheduled backup. I had no option but to reinstall, but haven't had this issue since.

[ghost]

This has happened to me before, too, and I also suspect it had to do with the scheduled backup. I had no option but to reinstall, but haven't had this issue since.

same for me. everything ok if i do not touch the scheduled backup function

[Backfighter]

Looks like and issue with my implementation of the storage access framework backend. Where did you store the file? Did you use any cloud provider (nextcloud, dropbox, etc.) or soemthing similar? If you just want to store the file on disk I recommend you to use the external storage backend instead.

I would also suggest you rename the issue to something more on topic. E.g. "[Bug] Exception on startup when using scheduled backup".

[ghost]

i set the scheduled backup to put the backup on removable micro-SD card.

right now, i manually make a backup via "storage access framework", which works fine. On May 12, 2021, 3:11 PM +0200, Backfighter @.***>, wrote:

Looks like and issue with my implementation of the storage access framework backend. Where did you store the file? Did you use any cloud provider (nextcloud, dropbox, etc.) or soemthing similar? If you just want to store the file on disk I recommend you to use the external storage backend instead. —You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

[Backfighter]

Was the storage access framework the only service you activated or did you also have a schedule for external storage?

I will try to reproduce the issue when I have time this week.

[ghost]

the only thing i remember is that i tapped the clock + arrow icon on the storage access framework page. to schedule an automatic backup. it seemed to work for a while. until i went back to the scheduler after roughly a week. it then crashed immediately on opening the scheduler. followed by the app refusing to start at all.

i had to reset the app to make the crashes go away. fortunately i had a somewhat recent manual backup so i did not have to input months of data again.....

i appreciate your attention for this issue. On May 13, 2021, 12:21 AM +0200, Backfighter @.***>, wrote:

Was the storage access framework the only service you activated or did you also have a schedule for external storage? I will try to reproduce the issue when I have time this week. —You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

[Backfighter]

It seems that somehow a wrong value for the storage access framworks backup folder was placed in the app settings. I have no idea how that happened and how to reproduce this. The only thing I might be able to do is prevent the whole app from crashing in that scenario in the future.

[ghost]

preventing the app from crashing would be a big improvement. i appreciate your efforts On May 14, 2021, 10:01 AM +0200, Backfighter @.***>, wrote:

It seems that somehow a wrong value for the storage access framworks backup folder was placed in the app settings. I have no idea how that happened and how to reproduce this. The only thing I might be able to do is prevent the whole app from crashing in that scenario in the future. —You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

[IdreesM0]

I had the same issue today. A fix (or maybe an in app warning before enabling it) would be truly appreciated.

[jeroenev]

Had same issue, thought i'd just clear the data and restore from backup Unfortunately the restore from backup option does nothing for me? I can select some folders but then it doesn't restore anything

[JosephChataignon]

I got the same issue just now, exactly 2 days (roughly at the same hour) after enabling regular backups using Nextcloud. The app just refuses to start now. Adding on this issue since it's the first one that shows when searching "moneywallet refuses to start"

[AkashRajpurohit]

Facing the same issue and restoring from a backup .mwbx file is importing only a very small subset of the data. I have around 2 years of data in this backup file and the restore shows around 20-30 entries only.

In the database.json file I can view the data is present but the restore is failing to pull all data, does anyone know solution for this?

[ialokim]

This is the same issue as #221, see the suggested workarounds over there.