- Joined
- Feb 4, 2017
- Messages
- 589
- Reaction score
- 159
- First Language
- English
Possibly a bug issue, but maybe resolvable in another fashion.
When attempting to use the folders created by Android deployment: audio, data, fonts, img, js
each one maintains meta data regarding erased/renamed files.
This has created complications when placing the folders into Android wrappers.
Does anyone know of an easy resolution? I have just been copy/paste files directly from my project and bypassing the MV deployment.
I wonder if another solution is creating all new folders within my project, but I am apprehensive that other meta data might exist in them and that I might harm my project.
Any advice or guidance is very welcome. Might just report as a bug and see if I can get feedback from Degica.
Admittedly, meta data is way outside my "wheelhouse."
When attempting to use the folders created by Android deployment: audio, data, fonts, img, js
each one maintains meta data regarding erased/renamed files.
This has created complications when placing the folders into Android wrappers.
Does anyone know of an easy resolution? I have just been copy/paste files directly from my project and bypassing the MV deployment.
I wonder if another solution is creating all new folders within my project, but I am apprehensive that other meta data might exist in them and that I might harm my project.
Any advice or guidance is very welcome. Might just report as a bug and see if I can get feedback from Degica.
Admittedly, meta data is way outside my "wheelhouse."
