Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2019.4.18f1
2021.2.0a2
Issue ID
1307154
Regression
No
[Android] Exporting project with Symlinked Sources on top of already exported project keeps copied .java and .kt files
How to reproduce:
1. Open the attached project (it has .java plugin)
2. In Build Settings enable "Export Project" and keep Symlink Sources off
3. Export project and specify folder where you want it to be exported
3.1 Examine exported project MyExportedProject/unityLibrary/src/java/com
3.2 Notice that it has unity/statictestj folder with JavaPlug.java
4. Go back to Unity and set Symlink Sources on in Build Settings
5. Export project to the same folder where it was exported in Step 3
Actual result: unity/statictestj folder with JavaPlug.java remains in the project and building project via Android Studio fails because of
duplicate class: com.unity.statictestj.JavaPlug
Expected result: When exporting on top of another project, files which are not needed should be deleted.
Reproduced: 2021.2.0a2, 2020.2.0b13, 2019.4.18f1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2021.2):
Fixed by incremental pipeline. 2021.2.a18