Hi,

The error “Git command line has exited with code 128” in Mendix usually indicates an authentication or connection issue, not that your project was deleted.

Since your team cannot see your commits and you cannot see theirs, your changes were likely committed locally but never pushed to Team Server.

First, check the Mendix Developer Portal → Repository/Changes to see if your commit exists there.

If it does not appear, your work is only on your local machine, so do not delete your current project folder yet.

Then try a fresh checkout:

1. Open Studio Pro
2. Go to File → Open App from Team Server
3. Download the project into a new empty folder

If the error persists, clear cached credentials:

• Open Windows Credential Manager
• Remove Mendix/Git related entries
• Restart Studio Pro and try again

If your local folder contains changes not on Team Server, you can recover them by exporting an .mpk (App → Export App Package) from the old project and importing it into the new checkout.

If this resolves your issue, please choose this answer as accepted so it can help others facing the same problem.

Hi,

This usually happens when the local Git repository gets out of sync or corrupted, which is why Studio Pro can no longer communicate properly with the Team Server. The error Git command line has exited with code 128 typically indicates a problem with the local repository rather than the Team Server itself.

A couple of things to clarify first:

If your teammates cannot see the commit in the Team Server repository, then the commit most likely never reached the remote repository. In other words, it was committed locally but the push failed.

Also, when you move the project folder and try to download again but still see the same error, it usually means Studio Pro is still referencing the corrupted local Git metadata.

The safest way to fix this is to completely remove the local repository and download a fresh copy from the Team Server.

What I normally do in this situation is:

1. Close Mendix Studio Pro.
2. Go to your Mendix project folder (usually under Documents\Mendix).
3. Delete the entire project directory including the hidden .git folder.
4. Open Mendix Studio Pro → App Explorer → Download from Team Server.
5. Download the project again to a new folder.

This forces Studio Pro to clone a completely clean copy of the repository from the Team Server.

If you had local changes that were not pushed, you may still find them in the old folder. In that case you can copy specific files (for example microflows or pages) from the old project into the new one and commit them again.

Also check that:

• Your Mendix account is still logged in in Studio Pro.
• Your Git credentials/token have not expired.
• You have permission to access the repository.

In most cases, doing a clean re-clone of the project from the Team Server resolves the code 128 issue.

Hi Muhmad wan,

I'd suggest you to duplicate your entire project folder and try opening the duplicated app and trying commiting through that app.

I've faced this same issue and this method helped me. Try this and let me know..!!

Thank you guys for all the answer it seems that it is indeed network connection issues. I have got three colleagues working on this project and it seems that those who are working in the same office also have the same issues. But the people who are working remotely doesnt have this issues. I have talked with my network administrator and still working on it.