Diagnosing indexing issues better?

[Andrew1]

It took a while but after opening obsidian android this morning, I had to wait a long time for the vault to reindex.

Thing is, during this time, the indexing message obscured part of the screen which meant that I couldn’t really use my notes. It shouldn’t do that IMHO; it should inform, but not fully interrupt.

Next, there doesn’t seem to be any log of what file it’s indexing. Thus, if it was to get stuck on a misformed file, we wouldn’t know what it’s getting stuck on ,without manually moving files about blind in trial and error.

1. isn’t there a log file?
2. isn’t there a command line tool to recursively check a vault for broken files?

[Quorkie]

Hi, I recently had the same, three times.

It is dutch, “During loading Obsidian an error has occurred”.
After this I’ve tried both options, both resulting in the following two screenshots:

This message is show in the top of the screen, while a (last time opened) mdfile is loaded and shown.
“Obs indexes the vault…This happens only once. Certain functions are not available until this is completed.”

“Indexing is completed.”

The first 2 times it started with the shown error.
Third time it didn’t show the error, only the indexing.

Result:
All md files look correct.
Yet, all backups are deleted (in standard plugin File Recovery). I might overstepped myself here, I set the amount of days to ~9999999. I would like to keep it on a long term for comparisons.

Possible causes:
First time: battery died; during booting the phone, I also opened Obsidian, perhaps it couldn’t create a snapshot of the loaded file (on time/in time, perhaps a time threshold), due to the load of the system while booting.
Second time: Google’s Playstore app is updated, available internal memory went to a low. I opened Obsidian from a sleeping instance/process, but vault had to be reloaded and then the error occurred.
Third time: unbeknown to me, alas.

Android version:
Version 1.4.1 (83)
API v1.0.3
No usage of community themes/plugins.

Extra question (perhaps for the devs):
Are the backup files in fact deleted? Does it free up the internal memory of the phone?
(I can’t see the location of the files, couldn’t find the system directory Sys dir with my app Total Commander, phone is not rooted etc.).

Note:
I know, I have to update to current version of the mobile app.
But perhaps it can still be mitigated even for newer versions, in order to prevent the result of loss of the snapshot/backup files.
In the near future I will update the app and check if it still occurs. If so, I will report it in the bugsection (with #Mobile? #Android?).

Thanks in advance,
Best regards,
Quorkie