[Bug]: broken for ios v16

[dougpagani]

Describe the bug

Can't initialize on mobile; I'm able to push just fine from WorkingCopy but not git-obsidian.

Relevant errors (if available)

No response

Steps to reproduce

Neither of these 3 have worked for me:

1. to empty GitHub repo from instantiated local vault

2. from instantiated github to empty obsidian vault

3. to non-existing github repo from instantiated local vault

(I've also tried 2 more of these via GitLab, to no avail)

Expected Behavior

I'm not sure if this ever worked for ios, so to be honest, i have no idea what to expect. Is this not supported yet? In the docs it seems to imply it is. Is there a known-working version I can roll back to?

Addition context

No response

Operating system

iOS

Plugin version

2.15.0

[dougpagani]

From a totally different workflow (new vault, keep it empty, clone from existing, declare a .obsidian, request deletion), i get different (also broken) behavior:

• took three attempts of a fresh vault until it stopped crashing on the download
• didn't work on a couple attempts of fresh "Init" instead of "clone from existing"; i assume this will never work
• won't push with just a "buffer" error message
• This plugin also seems to mangle the repo when it itself tries to initialize the local .git; WorkingCopy is unable to ever add the git-dir, with a stated failure message of: "failure to parse loose object: invalid header"

Reference screenshots:

[dougpagani]

i validated with another ios git provider to know it wasn't simply Working Copy (this one is PolyGit):

[dougpagani]

yet another piece of information for you: i'm able to fix the repo for WorkingCopy/PolyGit by just opening it up in ish shell and having it rebuild the index. Every time i open the vault with the git-obsidian plugin open, it bungles it again: (don't need to push for it to break it; pulls/commits from git-obsidian do it and even in rebuilding, the push still fails)

[dougpagani]

Alright well I give-up for now, i'll just use an appevent automation to trigger WorkingCopy and disable this plugin on mobile for now. Would be nice to get this to work since i was in the middle of setting up sync for a non-technical user when I encountered these bugs, for whom WC isn't really an option.

[bruzhmelev]

@dougpagani what tool do you use for accessing git on android?

[peteaah]

I was having issues getting a repo to work with obsidian-git following the regular mobile setup instructions
I got it to work on an iphone with ios 16.3, using itunes to drop the existing repo in place
I was able to get it working following the steps below, without using any other apps to manage git
Note: I am using a self-hosted git service called gogs, so authentication is handled exclusively with a username/password, I have not used other authentication methods

Close obsidian and ensure the repo is uploaded and up to date in the remote location

• Open obsidian for iOS
• Create a new vault, using the same name as the one uploaded to the repo
• connect iphone to computer and launch itunes
• Navigate into the connected device (not from the left-hand menu, see below:)
  
• Select "File Sharing" on the left-hand side
• Select Obsidian from the App list
• Drag and drop the folder where your obsidian repo is stored locally (the whole folder)
• Choose to overwrite matching files
• After the copy is complete, eject device from iTunes and open the Obsidian app

After that git-obsidian processes all of my requests the same way it does on desktop

[dougpagani]

@dougpagani what tool do you use for accessing git on android?

I don't know, I'm on ios for my phone. Not like you asked, but I was using a-shell for a partial (more than enough though) implementation of git. I would imagine it's even easier for android since it's linux-based, and you could just run normal git natively without any emulations, or like this repo uses, a javascript isomorphism.

[dougpagani]

@bruzhmelev

[dougpagani]

I ended up just disabling the plugin and implementing my own thing for mobile.

[GJRobert]

@dougpagani I am not facing problem on iOS 16 though