Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
I have a project which worked fine with the integrated GIT client. Now I can't update the solution or push the changes to the remote repository. The remote repository is hosted on a own server (no GitHub!).
If I want to update the solution I get
>Versionskontroll-Operation fehlgeschlagen:. Object reference not set to an instance of an object
If I try to push to the remote repository, I can't choose the remote repository. If I press the "push changes" button I get
>Invalid URI: The URI scheme is not valid.
The following command does work in the terminal
git push MyProjectOrigin develop
This is valid for two projects. At another project the "Projektmappe überprüfen und veröffentlichen" (check and publish changes) button is disabled. But I can right click a file > version control > check & publish to come to the same dialog. Don't know whats wrong in either cases. There is no hint at all.
This is the GIT config of one project
repositoryformatversion = 0
filemode = true
logallrefupdates = true
bare = false
name = someone
email = firstname.lastname@example.org
remote = .
merge = refs/heads/develop
remote = .
merge = refs/heads/master
url = email@example.com:ios/ProjectName.git
Xamarin Studio 5.10.1 (build 6)
Mac OS X 10.10.5
*** This bug has been marked as a duplicate of bug 36289 ***