Search Issue Tracker
Won't Fix
Votes
19
Found in
5.4.0f2
Issue ID
818258
Regression
No
[Android]The R.java generated by Unity during android compilation is too big which causes R.java refer to all resources.
Steps to reproduce:
1. Open "AndroidRClass.zip" project
2. Build project on android platform
3. Go to Temp/stagingArea/gen and in search field type R.java
-Observe that 3 same R.java files were generated
Actual result: The R.java generated by Unity during android compilation is too big. Each R.java refers to all resources. So each package imported to increase the fields references count which is limited to 65535 references.
Expected result: The R.java for each imported package and the project should only refer to its own resources.
Reproduced on: 5.5.0b5, 5.4.1f1, 5.3.6p4
Note: Similar problem is also discussed in https://forum.unity3d.com/threads/too-many-method-references-max-is-65536.327064/page-2
Comments (1)
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
lblast
Jul 14, 2017 18:10
In the Unity 5.6.1 patch notes (https://unity3d.com/unity/whats-new/unity-5.6.1), there is this comment on Gradle:
Android: Buildpipe - Fixed the user resources library build issues with Gradle.
Is this a fix to this issue?