UI locks up and doesn't seem to be doing anything

[MyMilkBiscuit]

I migrated from Unity 2019 to Unity 2022.1 a couple of days ago, and with it was forced to migrate from the old, official Github for Unity. I accidentally installed them both at the same time, but quickly uninstalled and cleared out all folders to make sure the DLLs were expunged.

Git for Unity seems to still be picking up my project's repository information, and can properly display the changes I've made since last pushing.

I can't push changes, even locally. The menu greys out as expected, but never actually does anything. Likewise, I cannot change the location of my git and git-lfs executables without the same problem. The UI basically doesn't function except for selecting changes and flipping through tabs. Every time I restart Unity or the domain refreshes, I am prompted to login to Github, but it doesn't seem to change anything or affect the log file at all. There are no exceptions being logged in the Unity console.

I've attached my latest log, but I'm not sure it has any descriptive info.

git-for-unity.log

[shana]

Hmmmm, yeah, not much in the logfile. It could be bad settings somewhere else, and for some reason it's not throwing an exception.

User settings are in %LOCALAPPDATA%\GitForUnity. This is saving options like trace logging flags.
System settings are in %PROGRAMDATA%\GitForUnity, and this has paths to git and state of git downloads and checking for updates.

The old GitHub for Unity should have different paths:
User settings are in %LOCALAPPDATA%\GitHubForUnity
System settings are in %PROGRAMDATA%\GitHubForUnity

Technically, GitHub for Unity would be stored in different folders but if they were both running at the same time, hmmm, maybe something got screwed up. Check if those folders exist, and you can try renaming them to something else, so your Git for Unity installation doesn't pick up anything and starts fresh.

I'm going to spend some hours tomorrow on GfU and fixing some bugs, I'll see if I can repro this and figure out what's going on - or at least improve the logging.

[MyMilkBiscuit]

Renaming the system settings to regenerate them seems to have fixed the problem! Looking at the differences between the two, for whatever reason the nonfunctional settings were forcing my git location to the system git location, but the regenerated one is using the EXEs shipped with Git for Unity. Maybe something is wrong with my system git installation? I'm not sure, but either way I'm so happy. Thank you so much! I can provide follow-up if you need it.

The old, nonfunctional system settings
systemsettings.txt

The regenerated, functional system settings
systemsettings.txt

(Both renamed to .txt to get around Github upload rules)

That being said, I also deleted my GitHubUnity folders in %PROGRAMDATA%, so if that was the problem, I can't be sure. Apologies for not conducting this experiment scientifically!

[shana]

hmmmmm! Git for Windows recently changed some paths around, so a newer git version might now not work properly with the current logic, while the "embedded" git version doesn't have that change yet. I ran into that when I started the work to upgrade the embedded git version, but that hasn't landed yet.

Good to hear it's working for you right now, I'll speed up the fixes for the new git format so you can go back to using the system git soon,