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 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.
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 ....
Created attachment 9147 [details]
To apply the patch, you should replace
C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets
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.
This issue was fixed on v3.9 and master.
It will be public with the next published build of v3.9.
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.
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.
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).
Seems fixed in latest beta.
Thanks Softlion for the confirmation.
As per comment 12, this issue is fixed.
Hence marking it as Verified.
Not sure which build SoftLion is mentioning. but I show the latest available beta build as of 1/6/15 is 220.127.116.11 (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 :|
I will try to clarify the status of this issue.
Currently, the public alpha and beta version is indeed 18.104.22.168 (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.
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!
sorry your are completly right