Bug 24633 - Incorrect/Wired codesign
Summary: Incorrect/Wired codesign
Status: RESOLVED DUPLICATE of bug 15489
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 5.7
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: master
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2014-11-18 19:02 UTC by Rustam Zaitov
Modified: 2014-11-19 15:33 UTC (History)
1 user (show)

Tags:
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:
Status:
RESOLVED DUPLICATE of bug 15489

Description Rustam Zaitov 2014-11-18 19:02:45 UTC
For deploying app to device I need codesign it first. Usually team provisioning profile works well. When I joined to multiple Apple Developer Programs I can face with troubles.

I have 2 devices (iPhoneA and iPhoneB) each device registered on different Apple Developer Account (MemberCenter)
iPhoneA registered within DeveloperAccountA
iPhoneB registered within DeveloperAccountB

TestCase 1:
On my mac I have only TeamProvisioningProfileA which includes iPhoneA (but it doesn't contain iPhoneB)
Within app project's settings set "Automatic" to "Identity" and "Provisioning Profile"
Connect iPhoneB to mac and try to deploy app via XS
XS builds app (success)
XS fail to deploy app (because app signed with TeamProvisioningProfileA which doesn't contain iPhoneB). This is a problem. XCode for such case failed on build phase with message about Provisioning profile which is a great clue for developer.

TestCase 2:
Generate TeamProvisioningProfileB which includes iPhoneB (but it doesn't contain iPhoneA)
XS builds app (success)
XS fail to deploy app (because XS selected wrong provisioning profile). Meanwhile XCode selects right profile. This is very wired for developer – he has both provisioning profiles but he can use only one device. As a workaround I can explicitly specify TeamProvisioningProfileB when I am going to deploy on iPhoneB.

Note: this is not theoretical problem, because each developer's account have 100 device limit.

Version 5.7 (build 435)
Comment 1 Jeffrey Stedfast 2014-11-19 15:33:51 UTC

*** This bug has been marked as a duplicate of bug 15489 ***