Hi guys, our game is under QA tests and they have found a crash which don’t know how to solve because the problem is in a file I don’t find in the project.
It crashes in different iOS devices with different iOS versions. To crash the game they have just to play as usual with wifi enabled. Then close the game, turn off the wifi and launch again the game. After a few seconds it crashes. I have symbolicated the crash with the next output:
SuiteQuaternionTestskUnitTestCategory::TestNormalizeSafeIfUnnormalized_DoesNotAlterQuaternionWhichIsVeryCloseToAlreadyNormalized::RunImpl() const (in bestarcadeshooter) (QuaternionTests.cpp:182) SuiteQuaternionTestskUnitTestCategory::TestNormalizeSafeIfUnnormalized_DoesNotAlterQuaternionWhichIsVeryCloseToAlreadyNormalized::RunImpl() const (in bestarcadeshooter) (QuaternionTests.cpp:177) SuiteQuaternionIntegrationTestskIntegrationTestCategory::TestEulerAngles_WorkInQuaternionTransformations::RunImpl() const (in bestarcadeshooter) (QuaternionTests.cpp:224) SuiteQuaternionIntegrationTestskIntegrationTestCategory::TestEulerAngles_WorkInQuaternionTransformations::RunImpl() const (in bestarcadeshooter) (QuaternionTests.cpp:228) SuiteQuaternionTestskUnitTestCategory::TestQuaternionMatrixEquivalenceTests::RunImpl() const (in bestarcadeshooter) (QuaternionTests.cpp:132) SuiteTransformChangeDispatchTestskUnitTestCategory::TestPermanentInterest_WhenComponentRemoved_IsSetCorrectlyHelper::RunImpl() (in bestarcadeshooter) (TransformChangeDispatchTests.cpp:584)
Anyone knows where do these files belong to (TransformChangeDispatchTests.cpp, QuaternionTests.cpp)? Searching through google didn’t take any results!
Those looks like Unity’s cpp-side unit tests for the Quaternions. Those should really not be in our Unity installs, and they should really, really not be in shipped builds!
Sounds like you should report a bug.
Here’s a funny thing - the first ones seems to be tests for what @superpig is talking about [in this post]( Script Data Upgrade page-2#post-3358298). It’s a small forum world.
If they’re what I think they are - Unity’s internal Unit tests - they shouldn’t be included in anything. That they even ship with Unity, so that it’s possible for Unity to include them in a build - is a mistake in and of itself. That there’s anything in the runtime that tries to make the unit tests run is a mistake. That it triggers from turning off the wifi starts getting into absurd joke territory.
Which means that there’s no reason to suspect that they won’t be included in a non-development build, but you might as well try.
You don’t happen to have a source code license? I can see something like this happening if someone with a source code license messes up when making a custom build of Unity.
It’s not a mistake. The tests are not included in release builds.
My guess is that this is actually nothing to do with the tests, but is either a symbolication error, or a stack smash. @levelappstudios could you post a single complete stack trace?