Bug 25531 - Xamarin IOs 3.8: DetectSigningIdentityTask error when referencing an ios lib
Summary: Xamarin IOs 3.8: DetectSigningIdentityTask error when referencing an ios lib
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: General ()
Version: 3.9
Hardware: PC Windows
: Normal normal
Target Milestone: 3.9
Assignee: Bugzilla
Depends on:
Reported: 2014-12-19 10:36 UTC by softlion
Modified: 2015-01-06 15:51 UTC (History)
5 users (show)

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

Patched Xamarin.iOS.Common.targets (38.05 KB, patch)
2014-12-19 13:30 UTC, Jose Gallardo

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 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 softlion 2014-12-19 10:36:28 UTC
To reproduce easily:
- use visual studio 2013 and beta channel
- create a new ios classic project A
- add a new ios classic library B to the solution
- in project A, add a reference to project B
- try to build

=> error DetectSigningIdentityTask ....
Comment 2 Jose Gallardo 2014-12-19 13:30:45 UTC
Created attachment 9147 [details]
Patched Xamarin.iOS.Common.targets

To apply the patch, you should replace 
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets
Comment 3 Jose Gallardo 2014-12-19 13:34:03 UTC
The root cause of the issue is already identified and we have a fix on track.

In the meantime, you can patch the failing targets file with the patch provided on Comment 2.

Comment 4 Jose Gallardo 2014-12-19 14:42:13 UTC
This issue was fixed on v3.9 and master.

v.3.9: 7e0c0a54be0a9473d56a5ca52768fbddb6830d43

Master: e877eb2ecd1563385008fe6b6cc2c1aeb0e23c76

It will be public with the next published build of v3.9.

Comment 5 Mohit Kheterpal 2014-12-22 10:48:39 UTC
I have verified this issue by following steps mention in bug description and I am able to build application successfully using XVS 3.9.226 as shown in screencast : http://screencast.com/t/fr7A6DvzAJ

Hence closing this issue.
Comment 6 softlion 2014-12-22 11:10:17 UTC
Ok it seems fixed, BUT it still happens - never on first compilation though. On 2nd compilation or any subsequent compilation, until you "clear" or "rebuild all" which fixes the problem.
Comment 7 Jose Gallardo 2014-12-22 13:06:37 UTC
Hi @softlion, 

First of all, thanks for filing the bug with those simple repro steps.

Regarding the error you're experience after the fix, I should say that unfortunately I was able to successfully build (not rebuild) after changing code on the library, then after changing code on the app, or after changing code on both projects without any need to Rebuild All or Clean.

The need for Rebuild or Clean actually seems to be a different issue, and we should be able to identify it from your logs, as we couldn't repro it on our end.

Can you please share us your build log? (Please change Tools - Options - Projects and Solutions - Build and Run - MSBuild project build output verbosity  to Diagnostic to get the most detailed log).

Kind regards,

Comment 11 softlion 2015-01-05 13:24:51 UTC
Seems fixed in latest beta.
Comment 12 softlion 2015-01-05 13:25:16 UTC
Seems fixed in latest beta.
Comment 13 Mohit Kheterpal 2015-01-06 07:55:48 UTC
Thanks Softlion for the confirmation.

As per comment 12, this issue is fixed.

Hence marking it as Verified.
Comment 14 xamarinbugzilla 2015-01-06 12:36:42 UTC
Not sure which build SoftLion is mentioning. but I show the latest available beta build as of 1/6/15 is (a6d269d) - which still shows the problem.

Maybe this is fixed in alpha? I'll try the workaround in #2 for now. Can't risk even more alpha instabilities :|
Comment 15 Jose Gallardo 2015-01-06 13:10:51 UTC
I will try to clarify the status of this issue.
Currently, the public alpha and beta version is indeed (a6d269d), and it doesn't include the fix.
The fix was included on 3.9.224 (7e0c0a5) and it was already verified by our QA team.
Unfortunately, the fixed version is not publicly available yet, but the patched target file from Comment 2 should help.
Comment 16 xamarinbugzilla 2015-01-06 13:18:26 UTC
Yes, the file from #2 does make building work again :) I'll keep an eye out for the new 3.9.224+ build as you and Mohit mentioned. Thanks!
Comment 17 softlion 2015-01-06 15:51:01 UTC
sorry your are completly right