Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove desktop.ini files on windows 10 before build or run #431

Closed
leobaccili opened this issue May 3, 2019 · 5 comments
Closed

Remove desktop.ini files on windows 10 before build or run #431

leobaccili opened this issue May 3, 2019 · 5 comments

Comments

@leobaccili
Copy link

leobaccili commented May 3, 2019

Feature Request

Motivation Behind Feature

Most users on Windows 10 have problems on build with de "desktop.ini" files.

Feature Description

Running this command before build or run keep the process more easy
del /S /Q /A:H desktop.ini

Alternatives or Workarounds

execute this command by yourself, like this
del /S /Q /A:H desktop.ini & cordova run android

@janpio
Copy link
Member

janpio commented May 3, 2019

Most users on Windows 10 have problems on build with de "desktop.ini" files.

I am a Windows 10 user and don't really know what you mean by that. Can you elaborate?

@leobaccili
Copy link
Author

The desktop.ini file is a hidden file used to store information about the arrangement of a Windows folder. Essentially, if the layout or settings for a folder are changed, a desktop.ini file is automatically generated to save those changes.

When i install a plugin or add a platform, many files are generated automatically. When i execute a run or build command, the cli return error indicating a problem with this files.

@janpio
Copy link
Member

janpio commented May 3, 2019

Ok, never noticed that here.

What error do you get because these files exist?

@nyambol
Copy link

nyambol commented Feb 1, 2022

This seems to be a known issue when storing data on Google Drive. I've been having it, myself. I moved that repo off the g drive.

@leobaccili
Copy link
Author

Jesus, i'm too late. Like @nyambol says, these errors occurs because the Google Drive, changing the storing to another place resolve this issues. Thanks and sorry for a too late answer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants