Git troubleshooting#
Git is in itself a very complex and powerful system that sometimes causes difficulties. In combination with external Git servers it can sometimes come to some mistakes, which are listed here.
General recommendations#
Keep your Git repository on an internal drive. Avoid mapped/ network drives or RAID management software that creates custom volumes.
Don’t put your Git repository in a Dropbox, Google Drive, Cloud Drive, NAS or similar
If you run out of storage, clear the Git cache by going to “Project Settings” / “Git” and clicking on “Clear Cache”.
Make sure that you have enough Git LFS storage on your Git hosting provider (GitHub, Azure, GitLab, etc).
Errors on Commit/ Staging#
These are problems that happen right after you press the “Commit” or “Push” button. During that process you see a huge progress indicator overlaying the application.
This problem often occurs if you are using a mapped/network or custom mounted drive with RAID management software. Git will not be stable here. It’s recommended that you work on an internal hard drive. If you have created your project on a mapped drive, simply cut and paste the project folder (including the _.approj file) to your internal drive. Then open Anchorpoint by double clicking on the _.approj file.
Errors on Push#
These are problems that happen after the commit, so when Anchorpoint is uploading the files in the background.
Cannot push to Azure or GitHub due to wrong username/ password#
Normally the credentials manager (a white popup dialog) should open. If it does not, go to “Project Settings” / “Git” and select “Update Credentials”.
If you have logged into Azure with a different account, logged into any Microsoft product (e.g. Office) with a different account, or have a Microsoft account with a different email, Anchorpoint may be using the wrong credentials. You can change this in the Windows Credential Manager. You can access it by pressing the WIN key and typing “Credential Manager”.
Entries like this confuse Anchorpoint. You may have other Microsoft related entries. Removing them does not cause harm. It’s just removing credentials from a cache. If an application needs them, it will ask you to enter them again.
Pushing on protected branches#
This can happen if you are pushing to the main branch, which may be protected by your git server admin. You can fix this by either asking the git server admin to give you more rights, or by pushing to a different branch.
A team member cannot join the Git repository#
This may be because the team member was added on the Git server. Besides Anchorpoint, you also need to invite him to your repository on GitHub, Azure DevOps, Gitea, etc. so that he has access to the data. If a member does not have access, Anchorpoint will display the name of the Git server where you need to add your team member in a message.
How to fix a broken Git repository#
If your timeline is empty, or you see certain error messages, that don’t make sense for you then your Git repository might be broken. This can happen due to various reasons:
You re-formatted your computer
Your computer crashed during a commit process
You deleted something in the .git folder
You were running out of disc space
You played around with some Git commands that you did not understand
The simplest way to fix that is to re-initialize the Git repository. Anchorpoint will create a backup of your project and then re-download all the files from the remote server if needed. Go to “Project Settings” / “Git” and pick Re-Initialize Project.
If this command did not solve the problem, you can also try this workaround:
Close Anchorpoint and close Unity/ Unreal and any other tool that you use right now
Rename your project folder to something like “myProjectFolder_backup”
Open Anchorpoint. It will ask you to re-join the Git repository. Pick a new empty folder and download your project again.
Then, from your backup (the renamed project folder) pick the files that you have changed and paste them into your newly downloaded project
Missing Files#
A file is not pushed to the Git repository on the server and Git cannot find the file when pulling changes. This error usually happens when someone pushed files to the Git repository with an ill-formed Git configuration. This can happen if you push with another Git client that is not configured correctly.
To fix this, tell the person that has pushed the commits to the server to do to the following:
Click on “Project Settings / Git”
Press the “Open Git Console / Terminal” command
type git lfs push origin YOUR_BRANCH_NAME –all, e.g. git lfs push origin main –all
After this command is finished, your should be able to pull or push the changes again.
Cannot store credentials#
This issue shows up when the Git is not able to store your credentials in the Windows Credentials Manager. Here is a discussion on GitHub if you want to know more. One of the reasons might be that the Credential Manager has too many credentials and you have to remove some old unused ones. You can access it by pressing the WIN key and typing “Credential Manager”, then click on “Windows Credentials” and remove some older entries.
Other issues#
We are constantly collecting issues to either improve Anchorpoint or to provide help. To make our life easier report us your issue by doing the following:
Close Anchorpoint
Go to C:/Users/USERNAME/AppData/Local/Anchorpoint/app-1.XX.X/scripts/win and open debug_mode.bat
If you are on macOS go to /Applications/Anchorpoint.app/Contents/MacOS/Anchorpoint and launch it with the “–debug” command at the end
Try to do what went wrong (e.g. committing files, pulling, opening the timeline, reverting etc.)
When the error shows up again send us a message by clicking on the “…” button in the top right corner
Describe your problem in the message. We will get a log file containing the error. This should give us all the information we need to fix it. Otherwise, you can also contact us at our Discord server
Troubleshooting Git servers