[Bug]: Cannot sync on iPhone and iPad. Obsidian crashes.

[WowLucy]

What happened?

I have turned on the debug level. The plugin is successful up to step 6. It is running and did not show step 7. After a really long time (like an hour), the entire app crashes. The plugin was okay before the update. After the update and I changed to using RClone to start a new sync, the sync never worked. I have 10,000+ files. The sync works on Mac, but when sync on iPhone and iPad, it does not work on both.

What OS are you using?

iOS (iPhone, iPad)

What remote cloud services are you using? (Please choose the specified one if it's in the list)

webdav (InfiniCloud (formally TeraCLOUD))

Version of the plugin

0.4.16

Version of Obsidian

1.5.12

Using password or not

• Yes.

Ensure no sensitive information

• I ensure that no sensitive information is submitted in the issue.

[WowLucy]

I tried multiple times on iPhone and Obsidian auto restarts. Remotely-save saying at stage generating plans. Cannot work. Please help. Thank you.

I set skip large files at 5MB. Works in a previous old version (0.3.25) of remotely-save but not with this new version.

[fyears]

how many files in your vault?

would you like to reduce the concurrency setting?

[WowLucy]

I have 10000+ files (plus files in .obsidian would be 17000+).
I set the concurrency to 1, but it still does not work. It is running in stage generating_plan for about 20min to an hour, and then Obsidian auto restarts.

I think the concurrency setting is related to the final syncing operation (in step 8) but Obsidian crashes before that (in step 7).

[fyears]

I have added two debug settings.

1. install latest remotely save (v0.4.21)

2. go to remotely save setting, scroll down to very end, you will see two new settings: "Enable Profiler Printing" and "Enable Profiler Recording Size", enable them both.
   

3. please install another plugin for recording logs easily on mobile: logstravaganza

4. enable logstravaganza,change the output format to "markdown code blocks".

5. trigger the sync of remotely save. in the meanwhile, logstravaganza should generate a file called console-log.<device>.md into the root of the vault. Even if your device crashs, the log file might have saved some hints.

6. disable logstravaganza after the first failed sync. so that the log file is not written later.

7. checkout the log file, and find out any useful info in the end of the log file. for example, you can see precisely where the app crashes, and you can see the size of some large objects (keyword: sizeof). remove any sensitive info and paste them into a github gist and paste a link here.
   

[fyears]

close due to no response. but anyways reducing large files should work