There's a growing and well-documented crash on Pixel devices running the new Android 14. In our game we're seeing them correspond to SIGABRTs. The stack indicates we're in some MIDI-related code but our game doesn't use MIDI at all. While we wait for Google to fix their code, does anyone know why our code is crashing in this stack even when there's no MIDI content, and how can we prevent AkMIDIEventCallbackInfo from being used?
0 libc.so +0x5c1a4 abort
1 libc.so +0x5e108 __fortify_fatal(char const*, ...)
2 libc.so +0x89a64 __FD_SET_chk
3 libAkSoundEngine.so +0x21a708 AkDefaultLogger(char const*) (AkSoundEngineStubs.cpp:188)
4 libAkSoundEngine.so +0x2182b0 CAkFileLocationBase::GetFullFilePath(unsigned int, AkFileSystemFlags*, AkOpenMode, char*) (AkFileLocationBase.cpp:180)
5 libAkSoundEngine.so +0x217398 AkCallbackSerializer::EventCallback(AkCallbackType, AkCallbackInfo*) (AkCallbackSerializer.cpp:229)
6 libAkSoundEngine.so +0x23483c CSharp_AkMIDIEventCallbackInfo_byValueLsb_get (SoundEngine_wrap.cxx:10429)
7 libAkSoundEngine.so +0x2ebd04 AkArray<MapStruct<float, CAkEdgePathSearch::EdgeData*>, MapStruct<float, CAkEdgePathSearch::EdgeData*> const&, AkArrayAllocatorNoAlign<(AkMemID)9>, AkGrowByPolicy_Proportional, AkAssignmentMovePolicy<MapStruct<float, CAkEdgePathSearch::EdgeData*> > >::Iterator::operator++() (AkArray.h:244)
8 libc.so +0xc9cc8 __pthread_start(void*)
9 libc.so +0x5dafc __start_thread
WWise 2021.1.13.2602
Unity 2022.3.10f1