- Home /
 
Android Development Build Crashing After Splashscreen
I'm working on a project and while it builds and runs fine for various Android devices development builds always crash immediately after the splash screen shows. I need a Development Build so I can use the profiler.
I've tried on numerous devices with different OS versions, and received the same results.
Here's the device log before the crash:
     Debug(18898)/Unity: Begin MonoManager ReloadAssembly 
     Debug(18898)/Unity: Platform assembly: /data/app/***.apk/assets/bin/Data/Managed/UnityEngine.dll (this message is harmless) 
     Debug(18898)/Unity: Loading /data/app/***.apk/assets/bin/Data/Managed/UnityEngine.dLess
 
 Warning(27516)/dalvikvm: JNI WARNING: illegal class name 'android.os.Build$VERSION' (FindClass)
 Warning(27516)/dalvikvm:              (should be formed like 'dalvik/system/DexFile')
 Warning(27516)/dalvikvm:              or '[Ldalvik/system/DexFile;' or '[[B')
 Info(27516)/dalvikvm: "main" prio=5 tid=1 NATIVE
 Info(27516)/dalvikvm:   | group="main" sCount=0 dsCount=0 obj=0x4160e6a0 self=0x415f4da0
 Info(27516)/dalvikvm:   | sysTid=27516 nice=0 sched=0/0 cgrp=apps handle=1074374736
 Info(27516)/dalvikvm:   | schedstat=( 0 0 0 ) utm=18 stm=9 core=0
 Info(27516)/dalvikvm:   #00  pc 00001260  /system/lib/libcorkscrew.so (unwind_backtrace_thread+27)
 Info(27516)/dalvikvm:   #01  pc 0005f78c  /system/lib/libdvm.so (dvmDumpNativeStack(DebugOutputTarget const*, int)+35)
 Info(27516)/dalvikvm:   #02  pc 00053f1e  /system/lib/libdvm.so (dvmDumpThreadEx(DebugOutputTarget const*, Thread*, bool)+289)
 Info(27516)/dalvikvm:   #03  pc 00053fae  /system/lib/libdvm.so (dvmDumpThread(Thread*, bool)+25)
 Info(27516)/dalvikvm:   #04  pc 0003a23e  /system/lib/libdvm.so
 Info(27516)/dalvikvm:   #05  pc 00042ec6  /system/lib/libdvm.so
 Info(27516)/dalvikvm:   #06  pc 004b61b8  /data/data/***/lib/libunity.so
 Info(27516)/dalvikvm:   at com.unity3d.player.ReflectionHelper.nativeProxyInvoke(Native Method)
 Info(27516)/dalvikvm:   at com.unity3d.player.ReflectionHelper.a((null):-1)
 Info(27516)/dalvikvm:   at com.unity3d.player.ReflectionHelper$1.invoke((null):-1)
 Info(27516)/dalvikvm:   at $Proxy0.run(Native Method)
 Info(27516)/dalvikvm:   at android.os.Handler.handleCallback(Handler.java:615)
 Info(27516)/dalvikvm:   at android.os.Handler.dispatchMessage(Handler.java:92)
 Info(27516)/dalvikvm:   at android.os.Looper.loop(Looper.java:137)
 Info(27516)/dalvikvm:   at android.app.ActivityThread.main(ActivityThread.java:4953)
 Info(27516)/dalvikvm:   at java.lang.reflect.Method.invokeNative(Native Method)
 Info(27516)/dalvikvm:   at java.lang.reflect.Method.invoke(Method.java:511)
 Info(27516)/dalvikvm:   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1004)
 Info(27516)/dalvikvm:   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:771)
 Info(27516)/dalvikvm:   at dalvik.system.NativeStart.main(Native Method)
 Info(27516)/dalvikvm: 
 Error(27516)/dalvikvm: VM aborting
 Error(27516)/libc: Fatal signal 11 (SIGSEGV) at 0xdeadd00d (code=1), thread 27516 (wa***)
 
              Answer by krisventure · Jun 24, 2016 at 05:02 AM
Having the same issue. Have you ever found an explanation?
Only solution I found is to not use Development Build. Not ideal...
Answer by ddoubleday · Jul 08, 2016 at 08:51 PM
I had the same problem. Figured out what caused the crash by switching to the il2cpp backend. The same crash happened but this time I got a meaningful stack trace and found which call was actually causing the problem.
Your answer
 
             Follow this Question
Related Questions
Android lag on Nexus 7 (2012) 0 Answers
Android thread causes crash? 1 Answer
Game App Crashes when Application.Quit() 0 Answers
When I start my game on Android this crashes (google play problem) 0 Answers