Bug 23747 - Cannot do a Clean/Rebuild All under latest version of Xamarin IDE
Summary: Cannot do a Clean/Rebuild All under latest version of Xamarin IDE
Status: VERIFIED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.18.0
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2014-10-10 16:19 UTC by David Schulte
Modified: 2014-10-20 13:58 UTC (History)
3 users (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:
VERIFIED FIXED

Description David Schulte 2014-10-10 16:19:08 UTC
After upgrading to the latest version of Xamarin today, I can no longer build after having done a clean and build all. I see the following error:

/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets: Error: Error executing task CopyAndConvertResources: Access to the path "ProjectPath/obj/Debug/res/layout/idd_aboutbox.xml" is denied. (TargetDroid)

I don't understand why the build is trying to reference this file - it certainly would not exist after having done a clean. The build all should be rebuilding it.

Below are the details about which version of Xamarin I'm running.
Thanks,
Dave

Xamarin Studio
Version 5.5 (build 227)
Installation UUID: 6f7c36db-b063-41d3-aa0d-4184811018e8
Runtime:
	Mono 3.10.0 ((detached/47db868)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 310000019

Apple Developer Tools
Not Found

Xamarin.Mac
Version:

Xamarin.iOS
Version: 8.2.0.193 (Starter Edition)
Hash: 959c1e4
Branch: 
Build date: 2014-10-03 00:25:37-0400

Xamarin.Android
Version: 4.18.0 (Business Edition)
Android SDK: /path/adt-bundle-mac-x86_64/sdk
	Supported Android versions:
		4.0.3  (API level 15)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
Java SDK: /usr
java version "1.7.0_17"
Java(TM) SE Runtime Environment (build 1.7.0_17-b02)
Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)

Build Information
Release ID: 505000227
Git revision: 7b721eeec7a2fa4c4f4de0ecd2aed4dc25edac95
Build date: 2014-10-02 15:53:38-04
Xamarin addins: 99ed56b428b31eba1efaace4d82188d6f334e6ca

Operating System
Mac OS X 10.9.5
Darwin hostname.local 13.4.0 Darwin Kernel Version 13.4.0
    Sun Aug 17 19:50:11 PDT 2014
    root:xnu-2422.115.4~1/RELEASE_X86_64 x86_64
Comment 1 David Schulte 2014-10-10 16:33:06 UTC
Reverting to the following Xamarin versions fixed things. Please also note that with the latest version I ran into a case where the initial build that I was doing never completed. It became unresponsive to the point I had to force quit the IDE. This is why I attempted the clean/rebuild all in the first place.
Dave

Xamarin Studio
Version 5.2.1 (build 1)
Installation UUID: 6f7c36db-b063-41d3-aa0d-4184811018e8
Runtime:
	Mono 3.10.0 ((detached/47db868)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 310000019

Apple Developer Tools
Not Found

Xamarin.iOS
Version: 8.2.0.193 (Starter Edition)
Hash: 959c1e4
Branch: 
Build date: 2014-10-03 00:25:37-0400

Xamarin.Android
Version: 4.14.0 (Business Edition)
Android SDK: /path/adt-bundle-mac-x86_64/sdk
	Supported Android versions:
		4.0.3 (API level 15)
		4.3   (API level 18)
		4.4   (API level 19)
Java SDK: /usr
java version "1.7.0_17"
Java(TM) SE Runtime Environment (build 1.7.0_17-b02)
Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)

Xamarin.Mac
Version:

Build Information
Release ID: 502010001
Git revision: d06832ce9807d6be24aca225457e8b37c7669f6f
Build date: 2014-08-07 12:10:47-04
Xamarin addins: 1de032531be4cecf2f39dbee3b87aac78204058c

Operating System
Mac OS X 10.9.5
Darwin hostname.local 13.4.0 Darwin Kernel Version 13.4.0
    Sun Aug 17 19:50:11 PDT 2014
    root:xnu-2422.115.4~1/RELEASE_X86_64 x86_64
Comment 2 Mohit Kheterpal 2014-10-13 08:05:17 UTC
I have tried to reproduce this issue by following steps :
1. create a template Android project 
2. Build solution
3. Clean all solution 
4. Rebuild all solution.

But it perform all actions successfully. we are unable to reproduce this issue at our end.

Could you please provide a test sample so that we can reproduce this issue at our end?

Thanks
Comment 3 David Schulte 2014-10-15 09:25:09 UTC
The bug appears to appear if the source layout file has mode 444, instead of 644. Try changing one of your layout files in what ever project you have defined to mode 444 and then rebuild. Our files are mode 444 by default, because they are pulled from a source code control environment, and would only be mode 644 if we are making a change.

e.g.,

$ cd path/Resources/layout
$ chmod 444 somelayout.axlml

Then build.
Comment 4 David Schulte 2014-10-15 09:26:13 UTC
I should emphasize that this issue is new. It does not occur with older versions of Xamarin.
Comment 5 David Schulte 2014-10-15 15:46:37 UTC
Mohit, have you been able to reproduce this now with my latest suggestions?
Comment 6 David Schulte 2014-10-17 07:26:16 UTC
Again, is anyone looking at this?
Comment 7 David Schulte 2014-10-19 19:29:03 UTC
Jonathan, can you please assign this issue to someone. Until this gets resolved, we cannot upgrade our Xamarin implementations.
Thanks,
Dave
Comment 8 Mohit Kheterpal 2014-10-20 13:51:46 UTC
@David

I am able to reproduce it with XA 4.18.0-34 by changing mode of .axml file to 444. But this issue is fixed in XA 4.18.0-39 and you will get the fixed build soon.

Thanks
Comment 9 David Schulte 2014-10-20 13:58:27 UTC
Thanks for confirming that this has been fixed.
Dave