Gitkraken stuck at opening repo

Question

Every time I open gitkrarken it gets stuck at opening repo icon. I can\'t open/clone/init repo. I heard some others have the same problem but no one seems to know why this i

Answer 1

In my case, I found out the problem was caused by the index file in ".git" folder.

The index is a binary file (generally kept in .git/index) containing a sorted list of path names, each with permissions and the SHA1 of a blob object; git ls-files can show you the contents of the index.

(Enter the link to know more)

Accidentally, I had deleted some files in my repository that's why it caused the index file changed. Therefore, my Gitkraken stuck in the infinity loop.

I just copied the index file in the previous updated repository and paste to the current repository. It works for me.

Answer 2

Check your project for large generated directories, like node_modules, which git isn't configured to ignore. If you don't tell git to ignore those (often very large) directories, Kraken will try to index them and will become overwhelmed by the task.

I had this problem too. Once I added the "node_modules" dir to the .gitignore file,

echo node_modules >> .gitignore

and restarted the Kraken client, it worked like a charm.

Answer 3

I had the same problem. Reading all of the above it appeared that my workflow was incorrect. I opened Excel and Notepad++ and suchlike to make changes to the repo and then opened GitKarken and was faced with the spinning circle. Of course all of these other programs took locks on the files. As soon as I closed all of the other programs and the restarted GitKraken it worked!! So more correct workflow would be to open GitKraken first and let it connect everything together, then do some work. Commit was no problem after that.

Answer 4

In our case there was a Latex document in the repository. Gitkraken could not open the repository.

Based on what @GeekyMonkey suggested, my student tried to start GitKraken after closing all files and shutting down his Tex editor.

It worked after that

Answer 5

For us, it was the fact that the one of our guys had the repo cloned to a OneDrive folder.

When the repo was in a OneDrive folder GitKraken would open and then constantly refresh so you couldn't click or do anything. You could describe it as GitKracken looked like it was 'flashing' on screen.

As soon as we moved the repo to a folder not monitored by OneDrive it worked just fine.

Answer 6

I had this problem using one repo, but not on others. The problem child was fairly large and complicated. I tried many of the solutions here to no avail. Then, I tried a pretty obvious patch - and upgraded the software. I went from GitKraken v3.x to v4.x and that did it!