Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.3.0f2
Issue ID
749524
Regression
No
[iOS] Application.version returns build number instead of version number
Application.version returns build number instead of version number. This issue only reproduces on iOS (it returns correct version numbers on Android).
Comments (5)
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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Sporkula
Oct 21, 2016 20:28
At the top of this page, in the banner if says "Status: Fixed in Unity 5.4.0"
Maisey
Sep 27, 2016 12:52
A related issue, but not exactly the same: When changing from 0.1 to 0.2, it returns 0.2 on all platforms (Android & UWP), but on iOS it returns 0.1 still (0.2 is set in both unity and xcode).
Currently running Unity 5.4.1f1.
jynerso
Apr 07, 2016 19:58
It causes serious crash on my game.. please include this fix soon.
swhitfield-nc2
Jan 12, 2016 18:32
Can we get more information on which patch this will be included in?
mark_madatom
Dec 16, 2015 10:38
This issue says "Status: Fixed", but there's nothing on the page telling me which version it's fixed in. Please could you add that information to your issue pages?