-
-
Notifications
You must be signed in to change notification settings - Fork 181
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
can't resolve config files with conflicts. #563
Comments
me the same,confuse |
I had the same issue. +1. |
Thank you for raising this issue! |
Thank you for your awaiting! |
Sorry 2 weeks I turned off advanced features (including hidden file sync) and rebuilt from local storage and that fixed the issue. I'll open another issue on this repo if the problem reoccurs after turning on the advanced features again. |
I still have this issue. Report:
Some DevLogs (I also have 4 files that obsidian reports as cannot be saved, might be deleted):
Beginning of logs:
|
Abstract
I can't resolve config files with conflicts.
Expected behaviour
Actually happened
Reproducing procedure
Note: If you do not catch the reproducing procedure, please let me know the frequency and signs.
Report materials
If the information is not available, do not hesitate to report it as it is. You can also of course omit it if you think this is indeed unnecessary. If it is necessary, I will ask you.
Report from the LiveSync
For more information, please refer to Making the report.
Report from hatch
Obsidian debug info
Debug info
Plug-in log
We can see the log by tapping the Document box icon. If you noticed something suspicious, please let me know.
Note: Please enable
Verbose Log
. For detail, refer to Logging, please.Plug-in log
Network log
Network logs displayed in DevTools will possibly help with connection-related issues. To capture that, please refer to DevTools.
Screenshots
If applicable, please add screenshots to help explain your problem.
Other information, insights and intuition.
Please provide any additional context or information about the problem.
The text was updated successfully, but these errors were encountered: