[AC-4149] Windows: intermitent EPERM error in i18n folders when compiling
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | n/a |
| Status | Closed |
| Resolution | Cannot Reproduce |
| Resolution Date | 2016-10-04T20:32:30.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | n/a |
| Labels | n/a |
| Reporter | Manuel Conde Vendrell |
| Assignee | Shak Hossain |
| Created | 2016-07-22T12:02:28.000+0000 |
| Updated | 2016-10-04T20:32:30.000+0000 |
Description
Since the change of *i18n&platform* folders to app folder, every 2 times I build I got this error:
{noformat}
[ERROR] : EPERM, operation not permitted 'W:\appc\project\i18n'
[ERROR] Alloy compiler failed
{noformat}
This happens in both of my PCs: home and office (always after installing 5.2.0 or upper). If I immediately build again, the error dissapear (or if I remove manually the i18n&platform folders). Normally, this happens in clicly: one time no error, next time error, again no error, again error...
The main problem is that, when using Liveview in office, if I save a change liveview is not able to recompile and, therefore, nothing happens in the app (no changes reflected, no restart... nothing). While in my home computer, if I save changes two times, first fails but second recompiles right, in office no matters the times I save changes, nothing happens.
I think is related to CLI, but in house I have SDK 5.2.2 and in office 5.3.1
Hello, This issue is not reproducible. Are you still having it?
Hi Sharif. Yes it happens always in both PCs (Win 7). I have a clear Win10 system with clear Appc install and there doesn't happen.
Hello, Do a clean setup on win 7 environment. See if the error occour then. Thanks.
I already did a clean setup of all Appc stuff, following my own tutorial: https://medium.com/all-titanium/reinstalling-appcelerator-titanium-on-windows-from-scratch-f7c50e2161f3, in both systems. Still the same. Seems that I will need a clean Win7 install, but I will not do that.
Hello, Whats the update on this, Do you still have the issue?
Hi Sharif. As I said, probably I will need a clean Win7 install to solve this problem (because in a Win10 clean install it works well), but I cannot do that right now (a lot of tools in my dev machine). So, ignore this problem by now.