Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2017.4
2019.3
2019.3.8f1
Issue ID
1244796
Regression
No
[iOS] UNITY_VERSION in UnityTrampolineConfigure.h is higher in earlier Unity versions compared to newer versions
Reproduction steps:
1. Open 2020.2.0aX and 2018.4.22f1 Editor folders
2. In both folders go PlaybackEngines -> iOSSupport -> Trampoline -> Classes
3. In both folders open UnityTrampolineConfigure.h
4. Inspect known Unity versions
Expected result: Unity version values for 2018.4 Editor are never higher than 2020.2 (these versions were used as an example)
Actual result: 2018422 > 202020
Reproducible with: 2017.4.40f1, 2018.4.22f1, 2019.3.13f1
Not reproducible with 2020.1.0b8, 2020.2.0a11 (note 3)
Note:
1. I noticed that all stable versions with Xf1 have a defined version that is longer in characters and therefore larger than the later versions
2. There are workarounds for this
3. 2020.1 does not have any versions that are higher than the ones in 2020.2 and 2020.2 is the newest stream so there is nothing to compare it to
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
- Input.GetKey() does not register key release when a specific key is pressed, and then released after opening a context menu
- Overlay Canvas is not visible when the Anti-aliasing field is set to FXAA and the Full Screen Pass Renderer Features’s Injection Point is set to “After Rendering Post Processing”
- The Particle System doesn't work when played through ContextMenu
- Crash on gles::UseGLSLProgram when shader fails to patch due to exceeding MAX_UNIFORM_LOCATIONS on Intel Tiger Lake chipset
- Crash on D3D12GetInterface when entering the Play mode
Resolution Note (fix version 2020.2):
Changes took place in 2020.2.0a14: We keep old defines around for backwards compatibility but we are forced to break direct numerical comparison