[TIMOB-6164] Tooling: building an Android project causes IOError 13 when resource files are read-only (Windows)
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2013-10-19T01:18:04.000+0000 |
| Affected Version/s | Release 1.7.2 |
| Fix Version/s | 2013 Sprint 21, 2013 Sprint 21 Core, Release 3.2.0 |
| Components | Tooling |
| Labels | androidbuild, cb-verified, qe-closed-3.2.0, triage |
| Reporter | Shawn Lipscomb |
| Assignee | Allen Yeung |
| Created | 2011-09-27T08:38:37.000+0000 |
| Updated | 2013-12-19T14:08:58.000+0000 |
Description
When files in the Resources directory (and below) have the read-only attribute set (as many source-control programs do), the build process regularly generates errors like this in the Application Installer console window:
[ERROR] IOError: [Errno 13] Permission denied: 'C:\\Titanium\\Workspace\\Proj1\\build\\android\\bin\\assets\\Resources\\tiapp.xml'
copy function in shutil.py (under plugins\com.appcelerator.titanium.python.win32_1.0.0.1312318466\python\Lib\shutil.py) to copy files into the build directory. That copy function calls copymode after copying the file. copymode (in the same file) calls os.chmod which, under Windows, can only copy the read-only attribute of a file. This is what's causing the problem. Since there's no need for the read-only attribute on any file in the build directory, this should be removed.
I was unable to reproduce this issue on windows. I have changed some of the images in my resources directory to read-only, and I don't run into this issue. Could you please provide a sample project and some reproduction steps for this issue? Thanks, Allen
Still happens to me all the time, now with Ti Studio 2.0.3.201205312012 and mobile SDK 2.1.0.v.... I can reproduce it easily by making tiapp.xml read-only and doing a clean build, followed by another build. Once a read-only file gets into the build directory, when that file is then changed, the next build fails with the IOError 13.
Reopening this ticket for further analysis.
I am currently having this problem Windows Server 2008 R2 Titanium build: 2.1.2.201208301612 Titanium SDK: 2.1.3.GA Connected to a TFS 2010 Server /build/ and /build/.* are in the .tpignore file I get the read only on the tiapp.xml in the build directory I uncheck the readonly flag on the tiapp.xml file in both the build directory as well as the Project directory Then I get the read error on the .fastdev.lock file Then I uncheck the readonly flag on that in both the build and project directories and finally it will build and launch.
I am currently having this problem on Mac OS X 10.8. Titanium Studio 3.0.2.201302191606 Titanium SDK 3.0.2.GA
10 watchers, priority set to high, but still no action. This is still a problem in SDK 3.1.1.GA
[~ayeung], might this be fixed with the new build process?
It could be... it's labeled as androidbuild, so we'll be going through to verify if it's still an issue.
Oh, I guess Chris just added it... so anyways, we'll check it out.
PR: https://github.com/appcelerator/titanium_mobile/pull/4781
Verified fixed on: Windows 7, 8 and 8.1 Windows Server 2008 Titanium Studio, build: 3.2.0.201312091613 Titanium SDK, build: 3.2.0.v20131218114845 CLI: 3.2.0-cr3 Alloy: 1.3.0-cr Created a default application for Android in a local workspace and made all files inside the Resources folder read-only. Also made the tiapp.xml file read-only. Also created a default application for Android on a network workspace from Windows 7 to Windows Server 2008. Both projects built and installed successfully to device and emulator. Closing.
To fully test, you have to build a project twice. The first time drops the files in the Build directory. The second time tries to overwrite those files.