-
Notifications
You must be signed in to change notification settings - Fork 246
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
[Bug]: Cant clone existing git repository #642
Comments
On some additional test with few files on repository appeared work properly, so it can be related with large ammount of files or size, but i suspect on git internal files, because cleaning repo does not solve the problem |
Same here |
Same happened on my iOS device. After I request pull for a set up repo in a fresh vault, the pop-up notification goes like: Moreover, if I keep trying to pull from the repo following the above process, it will eventually crash the whole Obsidian app, leaving it to be an unresponsive black screen. I have to kill Obsidian in iOS level. The git repo I was working with synced normally between my other macOS and Win devices. The vault is 34.3MB in size as I checked on my computer. |
I just had the same issue with the exact same behavior as @theIroaia |
Describe the bug
My Vault sync stopped working, and then when i tried to create another vault and repository, the same quiet behaviour occurs.
When triing to clone an existing repo, it starts to clone (tooltip notification), restart the vault, but nothing happen.
No files, no config, no branch, nothing.
On mobile version I cannot see my current branch, or other git configs
If repo with .obsidian file, then all configs are missing and git config are lost, and the repo substitution appears not to be replaced.
Relevant errors (if available) from notifications or console (
CTRL+SHIFT+I
)Steps to reproduce
Expected Behavior
Addition context
All operations are strange. Pull, push, fetch
Operating system
Android
Installation Method
None
Plugin version
2.22.0
The text was updated successfully, but these errors were encountered: