Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.1.X, 2019.2.X
Votes
0
Found in
2019.1.0a7
2019.1.6f1
2019.2
2019.3
Issue ID
1162227
Regression
Yes
[Android] Scripts changes do not take effect in builds after "Scripts only Build" has been turned off
To reproduce:
1. Open the attached project
2. Build and Run the "SampleScene" on Android device
3. Check the "Development Build" and "Scripts only Build" boxes
4. Uncomment 15th line in "TestScript" then "Patch and Run"
5. Uncheck "Scripts only Build", comment 15th line in "TestScript", uncomment 16th line in "TestScript"
6. Build and Run on Android device
Expected result: With "Scripts only Build" disabled, script changes take effect after building and running the apk
Actual result: With "Scripts only Build" disabled, script changes do not take effect after building and running the apk
Reproduced with: 2019.1.0a7, 2019.1.7f1, 2019.2.0b6, 2019.3.0a6
Not reproduced with: 2017.4.29f1, 2018.4.3f1, 2019.1.0a6
Regression started in 2019.1.0a7
Notes:
- Dev build has to be on
- Scene changes take effect, but not script changes
- Rebuilding Project Settings folder does not help
- Rebuilding the Library does not help
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment