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.
System.Net.WebException: The remote server returned an error: (405) METHOD NOT ALLOWED.
at System.Net.HttpWebRequest.CheckFinalStatus (System.Net.WebAsyncResult result) [0x002d9] in /private/tmp/monobuild/build/BUILD/mono-2.10.9/mcs/class/System/System.Net/HttpWebRequest.cs:1475
at System.Net.HttpWebRequest.SetResponseData (System.Net.WebConnectionData data) [0x00141] in /private/tmp/monobuild/build/BUILD/mono-2.10.9/mcs/class/System/System.Net/HttpWebRequest.cs:1300
I think this is from TF's last update - they mentioned that they REQUIRE HTTPS for uploads.
Same IPA via the browser works fine. But thats no fun!
I can reproduce this, if I use https instead it works fine.
Unfortunately it's not the first time it's happened, and their documentation still says "http": https://testflightapp.com/api/doc/, so I'm not sure we should change to use https in spite of their documentation.
In any case they'll probably have it fixed by the time a new MonoDevelop release is out, the quickest way to make it work again is probably to make them aware http doesn't work anymore.
is the URL in a config file somewhere so i can change it? if not, can it be?
Aaaaaaand testflight uploading is working again. yay!
Reopening, since I think it should be fixed/worked-around on our end. It's the second time it's happened, so I think it'll probably happen again.
rolf: what's the status of this?
Jeff: I think it's fixed. It's very very old, TF has been working fine for ages. (certainly since march 2012)