Bug 14496 - Publish to TestFlight dialog does not validate some invalid inputs
Summary: Publish to TestFlight dialog does not validate some invalid inputs
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Add-in ()
Version: 4.1.10
Hardware: PC Mac OS
: Lowest enhancement
Target Milestone: master
Assignee: Mike Krüger
Depends on:
Reported: 2013-09-06 15:31 UTC by PJ
Modified: 2014-04-04 14:55 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description PJ 2013-09-06 15:31:29 UTC
Another small enhancement here, but you can put just about anything in the dialog.

In most cases, you'll get a decent error message: http://screencast.com/t/XEG3huT3Q

In some cases, you don't, you get a WebException because the server returns 500 from the request sent.

For instance, enter a single space for the Api Token or Team Token and continue, you'll see it.

This is a very minor issue, but I saw it so I'm filing - no pressure krueger!

XS db76469e784f31468885b9cdaa7f8df4707d6e1d
Comment 1 Mikayla Hutchinson [MSFT] 2014-04-04 14:49:24 UTC
Android TestFlight no longer exists.
Comment 2 PJ 2014-04-04 14:55:17 UTC
Thanks! Have we already removed the whole tool? If not I can file another bug for that.