Search Issue Tracker
Fixed
Votes
1
Found in
Issue ID
758974
Regression
No
Editor and platform support can easily become out-of-sync
It seems far to easy to get the editor out-of-sync with a given player build platform. We should prevent the user from building in this situation. To reproduce this bug:
1. Install Unity version 5.3.1f1
2. Install the Unity Editor only, version 5.3.1p1 (I used this link: http://beta.unity3d.com/download/7d3d8e90548b/MacEditorInstaller/Unity-5.3.1p1.pkg from the normal QA patch releases page: http://unity3d.com/unity/qa/patch-releases)
3. Build an empty for iOS (which seems to work fine)
4. Open the generated Xcode project and attempt to build it. I see lots of errors like this:
Bulk_Generics_0.cpp:256:3: Use of undeclared identifier 'il2cpp_codegen_initialize_method'
These errors occur because the iOS player build is from version 5.3.1f1, which won't work with the code il2cpp.exe generates at version 5.3.1p1.
More generally, the Editor should probably detect this version mismatch and prevent the user from building.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
jonbro5556
Mar 16, 2016 22:36
this totally isn't fixed, as of 5.3.3f1. It seems like you could do a regression test on this no?