ARFoundation 2.1 examples when deployed always throw a FormatException Warning when the application launches.
Unity 2019.1.0f1
FormatException: Input string was not in a correct format.
at System.Number.ParseSingle (System.String value, System.Globalization.NumberStyles options, System.Globalization.NumberFormatInfo numfmt) [0x00000] in <00000000000000000000000000000000>:0
at System.Single.Parse (System.String s, System.Globalization.NumberStyles style, System.Globalization.NumberFormatInfo info) [0x00000] in <00000000000000000000000000000000>:0
at System.Single.Parse (System.String s, System.IFormatProvider provider) [0x00000] in <00000000000000000000000000000000>:0
at UnityEngine.XR.ARKit.ARKitImageTrackingSubsystem.RegisterDescriptor () [0x00000] in <00000000000000000000000000000000>:0(Filename: currently not available on il2cpp Line: -1)
FormatException: Input string was not in a correct format.
at System.Number.ParseSingle (System.String value, System.Globalization.NumberStyles options, System.Globalization.NumberFormatInfo numfmt) [0x00000] in <00000000000000000000000000000000>:0
at System.Single.Parse (System.String s, System.Globalization.NumberStyles style, System.Globalization.NumberFormatInfo info) [0x00000] in <00000000000000000000000000000000>:0
at System.Single.Parse (System.String s, System.IFormatProvider provider) [0x00000] in <00000000000000000000000000000000>:0
at UnityEngine.XR.ARKit.ARKitXRObjectTrackingSubsystem.RegisterDescriptor () [0x00000] in <00000000000000000000000000000000>:0(Filename: currently not available on il2cpp Line: -1)
This is a known issue and will be fixed shortly. It happens on iOS when the OS string contains a point revision, like "12.1.2" instead of just "12.1".
This also happens in the unity editor (2019.1), as the #ifdefine starts to late! (so scenes containing arkit don't work anymore - even when the gameobject is disabled)
It happens in the editor for the same reason -- we try to parse a string like "Mac OS 10.14.1" as a float. However, in the Editor, it shouldn't affect anything else; just an annoyance.
What are you waitiing for to push a fix for a bug stupid as this one?
I assume they have more important things to focus on since this issue doesn't cause any real problems.
What are you waitiing for to push a fix for a bug stupid as this one?
Since Monday is a holiday in the US, we decided to wait until the end of the long holiday weekend. Experience suggests pushing a fix and heading home for a long weekend does not serve our users well.
I assume they have more important things to focus on since this issue doesn't cause any real problems.
It causes problems on device as well, so it's a real problem, and we are taking it seriously.
Most helpful comment
Since Monday is a holiday in the US, we decided to wait until the end of the long holiday weekend. Experience suggests pushing a fix and heading home for a long weekend does not serve our users well.
It causes problems on device as well, so it's a real problem, and we are taking it seriously.