Iphone Obsidian Git Pull Broken, nothing has changed between today and yesterday

On mobile timeout is an issue. That’s why I opted for git with A-Shell.

Now I have JB, I no longer use A-Shell, either.

OK so you think using ish just won’t work in the future (maybe the vault just got too large and now push requests just time out?). Or what is the technical reason why it has stopped working?

The technical reason at Obsidian Git is mentioned at the plugin description.
I never used iSH, so not sure about timeout issues there.
Also, you can try adding some lines to your config that may help with RAM management:

	repositoryformatversion = 0
	filemode = true
	bare = false
	logallrefupdates = true
    packedGitLimit = 128m
    packedGitWindowSize = 128m
    deltaCacheSize = 128m
    packSizeLimit = 128m
    windowMemory = 128m
	active = .
[remote "origin"]
	url = https://github.com/<username>/<reponame>.git
	fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
	remote = origin
	merge = refs/heads/master
	repositoryformatversion = 0
  • I use master instead of main. You don’t need to worry about that. Just add the lines with core and pack.
    Not sure how much it helps. You need to add these (to at least the config file on your mobile device or maybe even to PC side) after initializing your git, I believe.

I have JB now and calling git status is extremely fast (less than 1 sec). Before on A-Shell it was 30-45 secs.

But, mind you, A-Shell doesn’t have git, only libgit2. On JB, I can use git. So not sure the RAM management would work with libgit2 – must check online docs.

Ended up fixing my issue by just cloning again. Somehow push works again. Don’t think it’s a timeout issue with the specs of the phone because pull and clone work just fine. Your solutions seem interesting but probably apply more to a-shell than ish. Would love to know why push breaks randomly on ish then gets fixed after recloning.

Still facing this issue. Cloning fixes it temporarily. If anyone has any insight let me know.

I can be anyone…

Try this:

Tried that and still get stuck here:

it seems that it gets stuck at the push and times our. Somehow cloning makes this not happen. Let me know if you understand why gino, didn’t mean to not include you.

Confident git authentication is working because it works after clone and on other devices. Pull and commit working but pushing being broken doesn’t make much sense to me. Not an internet issue either as it works after a fresh clone on same network.

You can clone and even pull from the remote but you won’t be allowed to push unless your authentification is done – at least on the SSH protocol* (you need private and public keys registered). Cause as I said I almost always used SSH, and while on iPadOS, I was unsuccessful caching in my credentials for HTTPS (in A-Shell; as I was not experienced at this at the time).
BUT: Obsidian Git should do this of itself. And as I said, it does use HTTPS. At least it was before. Not sure anything has changed.

I also recommend reaching out at the Issues page of the plugin and searching for a similar problem first.

* EDIT: Nor will you be allowed on HTTPS, either. If the repo is private, you need to use login and password/token.

Maybe I am not being clear, once I have cloned my phone is then able to push as normal for a bit. So I could not see it being an authentication issue, clearly authentication works briefly, as briefly I can clone, pull and push after I have cloned.

Will post on the issues page, didn’t find any similar issues.

Any other ideas? @gino_m

Installed Obsidian Git on a smaller vault to see how it goes. Nothing of the sort you are reporting happened here yet.

Let me know if you experience an issue with a larger vault.

Not going there, I’m afraid.
With the main vault, I use the methods detailed above.

Well I suppose this issue will remain. I’ve posted an issue to the github. If anyone else has any insight please let me know.

i’ve never been able to get obsidian git to work on iphone.

working copy is 100% worth it. coming from someone who was extremely reluctant to purchase at first.

1 Like

New tutorial if you’re interested:

Not sure that’s helpful as everything for me works up until the git push point (which is where it freezes). I assume this is just a problem with the way ish handles pushes.

I’ll look into it. Been very frustrated with ish.

Then try with A-shell. But memory issues happen there as well.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.