I am using Mendix 9.21.0 and received this error when I tried to pull the changes from my colleagues. LibGit2Sharp.NotFoundException: object not found - no match for id (78fa4b01ded8e16194815c432117638803117569) at LibGit2Sharp.Core.Ensure.HandleError(Int32 result) in /_/LibGit2Sharp/Core/Ensure.cs:line 154 at LibGit2Sharp.Core.Proxy.git_checkout_tree(RepositoryHandle repo, ObjectId treeId, GitCheckoutOpts& opts) in /_/LibGit2Sharp/Core/Proxy.cs:line 229 at LibGit2Sharp.Repository.CheckoutTree(Tree tree, IList`1 paths, IConvertableToGitCheckoutOpts opts) in /_/LibGit2Sharp/Repository.cs:line 1018 at LibGit2Sharp.Repository.FastForwardMerge(AnnotatedCommitHandle annotatedCommit, MergeOptions options) in /_/LibGit2Sharp/Repository.cs:line 1663 at LibGit2Sharp.Repository.Merge(AnnotatedCommitHandle[] annotatedCommits, Signature merger, MergeOptions options) in /_/LibGit2Sharp/Repository.cs:line 1548 at LibGit2Sharp.Repository.Merge(Branch branch, Signature merger, MergeOptions options) in /_/LibGit2Sharp/Repository.cs:line 1262 at Mendix.Modeler.VersionControl.Actions.GitMergeAction.Merge(IRepository repo, Branch featureBranch, Signature signature, FastForwardStrategy fastForwardStrategy) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.VersionControl\Actions\Git\GitMergeAction.cs:line 18 at Mendix.Modeler.VersionControl.Operations.Git.GitUpdateOperation.TryMerge(IRepository repo, Signature signature) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.VersionControl\Operations\Git\GitUpdateOperation.cs:line 97 at Mendix.Modeler.VersionControl.Operations.Git.GitUpdateOperation.DoUpdate(UpdateRequest updateRequest, Repository repo) in C:\Users\Autobuild\workspace\AppStudio4.0-Build\modeler\Mendix.Modeler.VersionControl\Operations\Git\GitUpdateOperation.cs:line 65 Can someone help with this issue?
asked
Plamen Draganov
1 answers
0
Do you have local uncommitted changes? If, not I would recommend deleting the folder locally and downloading from the version control sever.
Is it possible that someone renamed the remote branch?