Bug 8022 - M4A fails to build with 4.2.8 - missing a task
Summary: M4A fails to build with 4.2.8 - missing a task
Status: RESOLVED INVALID
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 4.2.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-10-26 12:30 UTC by Paul Johnson
Modified: 2012-12-11 22:41 UTC (History)
4 users (show)

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


Attachments
Log file from build (208.55 KB, text/plain)
2012-10-26 14:10 UTC, Paul Johnson
Details
my log.txt when I follow the steps in comment #1 (133.60 KB, text/plain)
2012-10-29 12:13 UTC, Jens
Details


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 INVALID

Description Paul Johnson 2012-10-26 12:30:10 UTC
After upgrading to 4.2.8 from 4.2.6, my project fails to build giving the error message

Error initializing task CheckDuplicateJavaLibraries: Not registered task CheckDuplicateJavaLibraries

If I regress back to 4.2.6, this error goes.
Comment 1 Jonathan Pryor 2012-10-26 13:25:01 UTC
Which Mono version are you using? Specifically, what's the output of:

    xbuild /version

I'm using 2.10.9.

Also, what happens if you enable diagnostic output?

    xbuild /v:diag YourProject.csproj > log.txt
Comment 2 Paul Johnson 2012-10-26 14:10:03 UTC
I'm using the same version as you. log.txt file attached
Comment 3 Paul Johnson 2012-10-26 14:10:59 UTC
Created attachment 2802 [details]
Log file from build
Comment 4 Jonathan Pryor 2012-10-26 15:12:50 UTC
Now I'm really confused; Attachment #2802 [details] doesn't contain any build errors:

> 	 0 Error(s)

Furthermore, it does contain CheckDuplicateJavaLibraries invocations:

>	Target _CheckDuplicateJavaLibraries:
>	Task "CheckDuplicateJavaLibraries"
>		Using task CheckDuplicateJavaLibraries from Xamarin.Android.Tasks.CheckDuplicateJavaLibraries, Novell.MonoDroid.Build.Tasks, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
>		  JavaSourceFiles:
>		  JavaLibraries:
>		  LibraryProjectJars:
>	Done executing task "CheckDuplicateJavaLibraries"
>	Done building target "_CheckDuplicateJavaLibraries" in project "/Users/PFJ/Developer/wowZapp/LaffOutLoud/wowZapp.csproj".

I don't see your error at all. Is there still a problem?
Comment 5 Paul Johnson 2012-10-26 16:13:08 UTC
Problem gone - now it's just telling me my copy is for evaluation purposes only!

3 reinstalls later and it kinda works

Closing the bug.
Comment 6 Jens 2012-10-29 12:12:41 UTC
I still see this bug, can it please be REOPENed? 
Thanks!

when I follow the steps in comment 1 there is no error too and the checkDuplicateJavaLibraries stuff is also in. I will attach it to this bug
Comment 7 Jens 2012-10-29 12:13:38 UTC
Created attachment 2807 [details]
my log.txt when I follow the steps in comment #1
Comment 8 Jonathan Pryor 2012-10-29 13:54:17 UTC
@Jens: I see the same thing in your attachment #2807 [details]:

>	Target _CheckDuplicateJavaLibraries:
>	Task "CheckDuplicateJavaLibraries"
>		Using task CheckDuplicateJavaLibraries from Xamarin.Android.Tasks.CheckDuplicateJavaLibraries, Novell.MonoDroid.Build.Tasks, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
>		  JavaSourceFiles:
>		  JavaLibraries:
>		  LibraryProjectJars:
>	Done executing task "CheckDuplicateJavaLibraries"
>	Done building target "_CheckDuplicateJavaLibraries" in project "/Users/jur/Projects/LetMeTalk/LetMeTalk_Android/LetMeTalk_Android.csproj".
...
> 	 0 Error(s)

There's no error there. :-/
Comment 9 Jens 2012-10-29 15:19:31 UTC
strange, it disappeared here too :-/

maybe a restart of monodevelop was needed after update or something like that?
I am sure that I still got the error even after the log.txt was created...

Ok, now I just need this "Deployment failed. The assembly directory could not be created" problem to go and I can test my app again... ;)
Comment 10 Jonathan Pryor 2012-10-29 17:13:08 UTC
> "Deployment failed. The assembly directory could not be created"

Two bits of info will help here:

1. Logcat output.
2. The $HOME/Library/Logs/MonoDevelop-3.0/AndroidTools*.log file for when you encountered the failure.
Comment 11 Jens 2012-10-29 22:23:42 UTC
hello jonathan,

I created bug 8053 for your pleasure and attached the log files you asked for to that bug :)

thanks!
Comment 12 Jonathan Pryor 2012-10-30 10:42:20 UTC
Looks like this bug isn't reproducible by the reporters.
Comment 13 Daniel Longhurst 2012-12-11 22:41:15 UTC
I got the same error as above after the update earlier today.  An additional re-start of MonoDevelop seems to "fix" the error.  I believe i was still in the initial run after updating when i first saw the error.