Bug 23685 - Support legacy Apple Developer IDs
Summary: Support legacy Apple Developer IDs
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 5.5
Hardware: PC Mac OS
: --- enhancement
Target Milestone: master
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2014-10-08 12:18 UTC by Cody Beyer (MSFT)
Modified: 2015-09-08 16:56 UTC (History)
2 users (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 Cody Beyer (MSFT) 2014-10-08 12:18:58 UTC
Older Apple Developer IDs are not in the form of email address and can contain invalid email characters. Devs who use these are unable to use Xamarin Studio for certain iOS functions, as email address is validated.

Comment 1 Jeffrey Stedfast 2014-10-08 12:20:29 UTC
What features? We no longer support Developer IDs at all and haven't since 5.0
Comment 2 Cody Beyer (MSFT) 2014-10-08 12:59:56 UTC
From User:

- Select "Build" > "Archive" menu item
- Click "Validate" button
- Enter "john doe" as the Username. An exception will result. "john doe" is
a valid format for an Apple Developer account ID.
Comment 3 Jeffrey Stedfast 2015-09-08 16:56:23 UTC
this was fixed