Log in or register to post comments

Android tutorial app via Unity 2017.2 crashing

October 12, 2017 - 11:59am #1

Hello - newbie here, first time using Vuforia.

I have followed the "getting started" tutorial here.  Runs great in the Unity player, it uses the host camera, recognizes the astronaut image and places a simple cube attached to the target / recognized object. No code change, just following the tutorial.

Now I Build and Run to my device (Google Pixel), and run the app.  See the Unity splash screen, then black screen for a few seconds, then hard CRASH.  Happens every time.

Captured some log info via adb logcat.  Not sure what to be looking for, but the below seems to be the offending piece.  Looking for any other ugly info in the log...  Trying to think of whatever other info is helpful. 

Targeting Android 7.1 Nougat, API level 25.  

Any thoughts on what else I can try or what's going wrong here? 

Thank you for any help!

 

10-12 11:32:32.157 16189 16189 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x6e756857 in tid 16189 (an.hellovuforia)

10-12 11:32:32.265 16288 16288 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

10-12 11:32:32.265 16288 16288 F DEBUG   : Build fingerprint: 'google/sailfish/sailfish:8.0.0/OPR3.170623.008/4294783:user/release-keys'

10-12 11:32:32.265 16288 16288 F DEBUG   : Revision: '0'

10-12 11:32:32.265 16288 16288 F DEBUG   : ABI: 'arm'

10-12 11:32:32.265 16288 16288 F DEBUG   : pid: 16189, tid: 16189, name: an.hellovuforia  >>> com.ikdan.hellovuforia <<<

10-12 11:32:32.265 16288 16288 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x6e756857

10-12 11:32:32.266 16288 16288 F DEBUG   :     r0 6e756863  r1 cabd52fc  r2 00000000  r3 00000009

10-12 11:32:32.266 16288 16288 F DEBUG   :     r4 ffc388b8  r5 6e756863  r6 cabd52b4  r7 00000000

10-12 11:32:32.266 16288 16288 F DEBUG   :     r8 00000000  r9 ffc38914  sl ffc388b8  fp ffc38bb4

10-12 11:32:32.266 16288 16288 F DEBUG   :     ip f0eacfac  sp ffc38870  lr f0e8916d  pc f01946a8  cpsr 800f0030

10-12 11:32:32.269 16288 16288 F DEBUG   :

10-12 11:32:32.269 16288 16288 F DEBUG   : backtrace:

10-12 11:32:32.270 16288 16288 F DEBUG   :     #00 pc 0000c6a8  /system/lib/libutils.so (_ZNK7android8String164sizeEv+3)

10-12 11:32:32.270 16288 16288 F DEBUG   :     #01 pc 000003d0  /data/data/com.google.tango/libfiles/armeabi-v7a/libtango_client_api.so (offset 0xa9000)

 

10-12 11:32:33.286   911  1582 I WindowManager: WIN DEATH: Window{b7ade92 u0 com.ikdan.hellovuforia/com.unity3d.player.UnityPlayerActivity}

10-12 11:32:33.344   911  5297 I ActivityManager: Process com.ikdan.hellovuforia (pid 16189) has died: fore TOP

10-12 11:32:33.348   911  5297 W ActivityManager: Force removing ActivityRecord{cc3ae39 u0 com.ikdan.hellovuforia/com.unity3d.player.UnityPlayerActivity t14634}: app died, no saved state

 

 

 

 

 

Android tutorial app via Unity 2017.2 crashing

October 16, 2017 - 4:19pm #6

I'm glad you were able to get it working on the newest Unity =)

Feel free to open another thread if you aren't able to resolve your issue with virtual buttons.

Thanks,

-Vuforia Support

Android tutorial app via Unity 2017.2 crashing

October 16, 2017 - 1:53pm #5

OK well that was it.  I was running with beta b2 version.  Uninstalled, installed latest 2017.2.0f3 and my simple app is working now.  No crash.

Confirmed in logs that it's using Vuforia SDK version 6.5.22 now.

To answer your next question, started a new project, imported the Unity SDK sample "Vuforia Core Samples" from the Asset Store, included all scenes, built and ran on my Pixel device.  All works fine (except the virtual buttons - will try to track that down later).

It looks like the latest Unity 2017.2.0f3 was JUST released last week (Oct 12).  So at the time I started looking at this, it was not available.  Bugs in the beta I was using I guess.

Thank you very much for your help. Greatly appreciated.

Android tutorial app via Unity 2017.2 crashing

October 13, 2017 - 3:06pm #4

I see this line in your log:

Vuforia SDK version 6.5.17

Which version of Unity are you using? The official release version of Unity 2017.2.0f3 should have 6.5.22.

Also, would you be able to open a new project and import the sample project, then build it to device? I'm curious if there is a missing setting that the samples might have set.

Thanks,

-Vuforia Support

Android tutorial app via Unity 2017.2 crashing

October 13, 2017 - 10:36am #3

Thank you for the reply.  I executed the adb command you provided, and the app installed fine.  Ran it, and see the same behavior - Unity splash screen then a second or so later, hard crash.  

By the way - that's the APK that was created by Unity in the build & run command.

Captured some adb logcat output, attached. 

Guessing at some of the pertinent info (see full log, attached):

10-13 10:28:17.424  2960  2983 E Unity   : Unable to find AudioPluginMsHRTF

10-13 10:28:17.425  2960  2983 E Unity   : Unable to find libaudioplugingvrunity

10-13 10:28:17.426  2960  2983 E Unity   : Unable to find AudioPluginOculusSpatializer

10-13 10:28:17.426  2960  2983 E Unity   : Unable to find audioplugingvrunity

10-13 10:28:17.427  2960  2983 E Unity   : Unable to find unitygar

10-13 10:28:17.427  2960  2983 E Unity   : Unable to find libAudioPluginOculusSpatializer

10-13 10:28:17.428  2960  2983 E Unity   : Unable to find libtango_3d_reconstruction_api

 

10-13 10:28:17.630   707   741 E ANDR-PERF-OPTSHANDLER: Warning: Resource [2, 0] not supported for core 1. Instead use resource for core 0

10-13 10:28:17.630   707   741 E ANDR-PERF-RESOURCEQS: Failed to apply optimization [2, 2, 0]

 

10-13 10:28:22.318  2960  2983 E libEGL  : call to OpenGL ES API with no current context (logged once per thread)

 

10-13 10:28:23.194  2960  2960 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x6e756857 in tid 2960 (an.hellovuforia)

10-13 10:28:23.276  3057  3057 W crash_dump32: type=1400 audit(0.0:12173): avc: denied { search } for name="com.google.tango" dev="sda35" ino=2449718 scontext=u:r:crash_dump:s0:c512,c768 tcontext=u:object_r:app_data_file:s0:c512,c768 tclass=dir permissive=0

10-13 10:28:23.335  3057  3057 I crash_dump32: obtaining output fd from tombstoned

10-13 10:28:23.338   710   710 I /system/bin/tombstoned: received crash request for pid 2960

10-13 10:28:23.342  3057  3057 I crash_dump32: performing dump of process 2960 (target tid = 2960)

10-13 10:28:23.342  3057  3057 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

10-13 10:28:23.342  3057  3057 F DEBUG   : Build fingerprint: 'google/sailfish/sailfish:8.0.0/OPR3.170623.008/4294783:user/release-keys'

10-13 10:28:23.342  3057  3057 F DEBUG   : Revision: '0'

10-13 10:28:23.343  3057  3057 F DEBUG   : ABI: 'arm'

10-13 10:28:23.343  3057  3057 F DEBUG   : pid: 2960, tid: 2960, name: an.hellovuforia  >>> com.ikdan.hellovuforia <<<

10-13 10:28:23.343  3057  3057 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x6e756857

10-13 10:28:23.343  3057  3057 F DEBUG   :     r0 6e756863  r1 edc85df4  r2 00000000  r3 00000009

10-13 10:28:23.343  3057  3057 F DEBUG   :     r4 ffc388b8  r5 6e756863  r6 d168656c  r7 00000000

10-13 10:28:23.343  3057  3057 F DEBUG   :     r8 00000000  r9 ffc38914  sl ffc388b8  fp ffc38bb4

10-13 10:28:23.343  3057  3057 F DEBUG   :     ip f0eacfac  sp ffc38870  lr f0e8916d  pc f01946a8  cpsr 800f0030

10-13 10:28:23.346  3057  3057 F DEBUG   :

10-13 10:28:23.346  3057  3057 F DEBUG   : backtrace:

10-13 10:28:23.346  3057  3057 F DEBUG   :     #00 pc 0000c6a8  /system/lib/libutils.so (_ZNK7android8String164sizeEv+3)

10-13 10:28:23.346  3057  3057 F DEBUG   :     #01 pc 000003d0  /data/data/com.google.tango/libfiles/armeabi-v7a/libtango_client_api.so (offset 0xa9000)

 

 

 

 

Android tutorial app via Unity 2017.2 crashing

October 12, 2017 - 1:53pm #2

Hello danhik,

It's possible you are running into a permissions issue. Could you try reinstalling the apk on your device using the following command: "adb install -r -g <apk location>"

This should reinstall the app with all permissions so we can see if that is indeed the culprit.

Thanks,

-Vuforia Support

Log in or register to post comments