I understand every application must have an AndroidManifest.xml file in its root directory that provides essential information about the app to the Android system, which the system must have before it can run any of the app's code.
When one writes a plug-in for other applications (such as Unity3D) to do something on an Android device, they usually end up having to place the 2 files called AndroidManifest.xml and classes.jar in Assets/Plugins/Android/libs of their Unity app, but what if you already have similar files in your "libs" folder?
For example, what if your Unity project already has "classes.jar" and "AndroidManifest.xml" due to other plug-ins being used in the app?
What do you do in this situation?
When one writes a plug-in for other applications (such as Unity3D) to do something on an Android device, they usually end up having to place the 2 files called AndroidManifest.xml and classes.jar in Assets/Plugins/Android/libs of their Unity app, but what if you already have similar files in your "libs" folder?
For example, what if your Unity project already has "classes.jar" and "AndroidManifest.xml" due to other plug-ins being used in the app?
What do you do in this situation?