Since the issue seems fixed after the Oculus API update in 2018.3, there's little merit in backtracing where it broke

To reproduce:
1. Open the attached project "VikingVillageAndroidCrash.zip"
2. Build and Run on Oculus GO
3. Observe the application on launch

Result: application crashes

Reproduced in: 2017.4.24f1
Not reproduced in: 2018.3.11f1, 2019.1.0b9, 2019.2.0a10

Note: part of crash stack trace (application):

03-26 14:37:25.958 32346 32407 E CRASH : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr cef0e4e8
03-26 14:37:25.958 32346 32407 E CRASH : * * * * * * * * * * * * * * * *
03-26 14:37:25.958 32346 32407 E CRASH : Build fingerprint: 'oculus/vr_pacific/pacific:7.1.2/N2G48H/223630.6800.245:user/release-keys'
03-26 14:37:25.958 32346 32407 E CRASH : Revision: '0'
03-26 14:37:25.965 32346 32407 E CRASH : pid: 32346, tid: 32407, name: UnityPreload >>> com.oculus.VikingVillageAndroidCrash <<<
03-26 14:37:25.965 32346 32407 E CRASH : r0 cef0e540 r1 00000400 r2 000000ff r3 0000024c
03-26 14:37:25.965 32346 32407 E CRASH : r4 c8977690 r5 00000006 r6 c8977690 r7 00000006
03-26 14:37:25.965 32346 32407 E CRASH : r8 00000166 r9 0000000b sl cef2ba1c fp c301abd7
03-26 14:37:25.965 32346 32407 E CRASH : ip d57da684 sp cef0e4e0 lr d4832594 pc d48310b4 cpsr 0000000b