Removes previous files from an intermediate build directory, which could cause erroneous uploads if a SO file had been moved on the filesystem. Additionally this changeset prevents libunity.so, libil2cpp.so, and libmain.so from being
Changeset
The gradle plugin copies SO files to an intermediate build directory to take advantage of gradle's task caching.
If a build occured, an SO file was removed/renamed in the project, and then another build occurred, the removed/renamed SO file incorrectly remains in the build directory and is uploaded. The fix for this is to clear out the directory when running the task, which is done for both the Unity/NDK generation tasks.
Additionally, the BugsnagGenerateNdkSoMappingTask tries to generate NDK mapping files for libunity/libmain/libil2cpp, which have been ignored to avoid spamming the build log with the following warning:
Bugsnag: Skipping upload of empty/invalid mapping file: intermediates/bugsnag/soMappings/ndk/armeabi-v7a/libunity.so.gz
Testing
Manually verified that no warning is present in the build log, and that only the relevant files are copied to the intermediate directory on a build that uses cache.
Goal
Removes previous files from an intermediate build directory, which could cause erroneous uploads if a SO file had been moved on the filesystem. Additionally this changeset prevents
libunity.so,libil2cpp.so, andlibmain.sofrom beingChangeset
The gradle plugin copies SO files to an intermediate build directory to take advantage of gradle's task caching.
If a build occured, an SO file was removed/renamed in the project, and then another build occurred, the removed/renamed SO file incorrectly remains in the build directory and is uploaded. The fix for this is to clear out the directory when running the task, which is done for both the Unity/NDK generation tasks.
Additionally, the
BugsnagGenerateNdkSoMappingTasktries to generate NDK mapping files forlibunity/libmain/libil2cpp, which have been ignored to avoid spamming the build log with the following warning:Testing
Manually verified that no warning is present in the build log, and that only the relevant files are copied to the intermediate directory on a build that uses cache.