![]() We'll also be testing on some more devices in the next few days so I'll update with more info.Īs yet we've not been able to distil the problem into a 100% reproducible test project. We will investigate 's interface idea and report back. Samsung Galaxy Note 8.0 (Android 4.4.2).Kindle Fire HDX 8.9 (3rd Gen) (Fire OS 4.5.1).Here is a list of the devices we have tested on: As says, it's as though the code/stack has been altered on device. Requires a minimum of Android 4.4 (KitKat). This is a fork of BOOMiks Quest Player, an Android port of Quest Soft Player, tested on a 7' Amazon Fire Tablet (Android 5.1.1) and a Nexus Galaxy (Android 4.4.4). Static analysis finds no call from one method in the stacktrace to the next. Fork of BOOMiks Quest Player for Android, an apk that runs QSP games. The Unity stacktrace shows a code path that should not (cannot) happen. In a fairly reproducible case (~75%) our game will crash with Fatal signal 11 (SIGSEGV) having first logged an error from Unity. We have had similar symptoms when testing Android built with Unity 4.5.5.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |