Welcome to the Oculus Developer Forums!

Your participation on the forum is subject to the Oculus Code of Conduct.

In general, please be respectful and kind. If you violate the Oculus Code of Conduct, your access to the developer forums may be revoked at the discretion of Oculus staff.

Globally signed apk crashes on launch

dletozeundletozeun Posts: 26
edited May 2015 in VR Jam 2015
Hello,

After having uploaded my apk on the Global Signing tool page, downloaded it and installed it again on my gear, the app is lauching without stereo and crashing fews seconds later.

In logcat I get the following errors :
05-10 16:01:04.258: I/Unity(7225): AndroidJavaException: android.content.ActivityNotFoundException: Unable to find explicit activity class {com.oculus.home/com.oculus.home.HomeActivity}; have you declared this activity in your AndroidManifest.xml?
05-10 16:01:04.258: I/Unity(7225):   at UnityEngine.AndroidJNISafe.CheckException () [0x00000] in <filename unknown>:0 
05-10 16:01:04.258: I/Unity(7225):   at UnityEngine.AndroidJNISafe.CallStaticVoidMethod (IntPtr clazz, IntPtr methodID, UnityEngine.jvalue[] args) [0x00000] in <filename unknown>:0 
05-10 16:01:04.258: I/Unity(7225):   at UnityEngine.AndroidJavaObject._CallStatic (System.String methodName, System.Object[] args) [0x00000] in <filename unknown>:0 
05-10 16:01:04.258: I/Unity(7225):   at UnityEngine.AndroidJavaObject.CallStatic (System.String methodName, System.Object[] args) [0x00000] in <filename unknown>:0 
05-10 16:01:04.258: I/Unity(7225):   at OVRManager.Awake () [0x00000] in <filename unknown>:0 

It was working fine on my note 4 while building with its osig file. Like the log says there is no mention of any Android activity "com.oculus.home/com.oculus.home.HomeActivity" in my Unity project and the AndroidManifest.xml file.

Here is the manifest file:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.Oculus.Integration" android:versionName="1.0.0" android:versionCode="1">
  <supports-screens android:smallScreens="true" android:normalScreens="true" android:largeScreens="true" android:xlargeScreens="true" android:anyDensity="true" />
  <application android:icon="@drawable/app_icon" android:label="@string/app_name" android:theme="@android:style/Theme.Black.NoTitleBar.Fullscreen" android:debuggable="false">
    <meta-data android:name="com.samsung.android.vr.application.mode" android:value="vr_only"/>
    <activity android:name="com.unity3d.player.UnityPlayerNativeActivity" android:label="@string/app_name" android:screenOrientation="landscape" android:launchMode="singleTask" android:configChanges="screenSize|orientation|keyboardHidden|keyboard">
      <intent-filter>
        <action android:name="android.intent.action.MAIN" />
        <category android:name="android.intent.category.LAUNCHER" />
      </intent-filter>
      <meta-data android:name="unityplayer.UnityActivity" android:value="true" />
      <meta-data android:name="unityplayer.ForwardNativeEventsToDalvik" android:value="false" />
    </activity>
  <activity android:name="com.oculusvr.vrlib.PlatformActivity" android:theme="@android:style/Theme.Black.NoTitleBar.Fullscreen" android:launchMode="singleTask" android:screenOrientation="landscape" android:configChanges="screenSize|orientation|keyboardHidden|keyboard">
      </activity>
  </application>
  <uses-sdk android:minSdkVersion="19" android:targetSdkVersion="19" />
  <uses-feature android:glEsVersion="0x00030000" />
  <uses-permission android:name="android.permission.INTERNET" />
  <uses-permission android:name="android.permission.WAKE_LOCK" />
  <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
  <uses-permission android:name="android.permission.CAMERA" />
</manifest>

I can't find at the moment the reason why it is looking for this activity name. Did someone experienced the same issue ?

Thank you for your help.

Comments

  • dummyboydummyboy Posts: 11
    I have very similar problem. After I use global signing tool and download the application, it crashed on start and I my phone ends showing oculus home,

    I can see exactly the same behaviour if i remove my oculussig file from assets.
    I did make sure that entitlement is off.

    Below I past my log.
    I/OpenGLRenderer( 3509): HWUI protection enabled for context ,  &this =0xaf664fd8 ,&mEglDisplay = 1 , &mEglConfig = -1732873968 
    
    D/mali_winsys( 3509): new_window_surface returns 0x3000,  [1760x706]-format:1
    
    D/CustomFrequencyManagerService( 3509): releaseDVFSLockLocked : Getting Lock type frm List : DVFS_MIN_LIMIT  frequency : 1800000  uid : 1000  pid : 3509  tag : [email protected]
    
    W/ActivityManager( 3509): mDVFSHelper.release()
    
    I/Timeline( 3509): Timeline: Activity_windows_visible id: ActivityRecord{dacbc13 u0 com.oculus.home/.HomeActivity t416} time:121984026
    
    D/KeyguardUpdateMonitor( 3757): received broadcast android.intent.action.BATTERY_CHANGED
    
    D/KeyguardUpdateMonitor( 3757): handleBatteryUpdate
    
    D/STATUSBAR-PhoneStatusBar( 3757):  mBrightnessEnablebySettings = true mBrightnessEnablebyBattery = true mBrightnessEnablebyDisableFlag = true mPmsBrightnessEnablebySettings = true
    
    D/CrashAnrDetector( 3509): Build: samsung/treltexx/trelte:5.0.1/LRX22C/N910CXXU1BOC3:user/release-keys
    
    D/CrashAnrDetector( 3509): Hardware: universal5433
    
    D/CrashAnrDetector( 3509): Revision: 21
    
    D/CrashAnrDetector( 3509): Bootloader: N910CXXU1BOC3
    
    D/CrashAnrDetector( 3509): Radio: unknown
    
    D/CrashAnrDetector( 3509): Kernel: Linux version 3.10.9-4456638 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Fri Mar 13 15:44:47 KST 2015
    
    D/CrashAnrDetector( 3509): 
    
    D/CrashAnrDetector( 3509): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    
    D/CrashAnrDetector( 3509): Build fingerprint: 'samsung/treltexx/trelte:5.0.1/LRX22C/N910CXXU1BOC3:user/release-keys'
    
    D/CrashAnrDetector( 3509): Revision: '21'
    
    D/CrashAnrDetector( 3509): ABI: 'arm'
    
    D/CrashAnrDetector( 3509): pid: 21421, tid: 21460, name: UnityGfxDeviceW  >>> com.oculusvr.comawakes <<<
    
    D/CrashAnrDetector( 3509): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
    
    D/CrashAnrDetector( 3509):     r0 00000000  r1 ffffee34  r2 0012bba0  r3 9cdffdb0
    
    D/CrashAnrDetector( 3509):     r4 a0c80040  r5 b4ef9900  r6 00000000  r7 00000000
    
    D/CrashAnrDetector( 3509):     r8 b3976208  r9 b3976208  sl b6f85b9d  fp 9cdffdb0
    
    D/CrashAnrDetector( 3509):     ip b6fd872c  sp 9cdffd60  lr a0261148  pc 9ff714d0  cpsr 60070010
    
    D/CrashAnrDetector( 3509):     d0  0000000039ddc619  d1  0000000000000498
    
    D/CrashAnrDetector( 3509):     d2  00000000000008a0  d3  0000000000000d38
    
    D/CrashAnrDetector( 3509):     d4  0000000000001000  d5  000000009ccad000
    
    D/CrashAnrDetector( 3509):     d6  0000000000000064  d7  0000000000000499
    
    D/CrashAnrDetector( 3509):     d8  3e8000003f400000  d9  0000000000000000
    
    D/CrashAnrDetector( 3509):     d10 0000000000000000  d11 0000000000000000
    
    D/CrashAnrDetector( 3509):     d12 0000000000000000  d13 0000000000000000
    
    D/CrashAnrDetector( 3509):     d14 0000000000000000  d15 0000000000000000
    
    D/CrashAnrDetector( 3509):     d16 3ff1a0dfdf336800  d17 3ff19f2453016800
    
    D/CrashAnrDetector( 3509):     d18 0000000000000005  d19 0000000000000064
    
    D/CrashAnrDetector( 3509):     d20 0000000000000069  d21 0000000000000000
    
    D/CrashAnrDetector( 3509):     d22 000000000000003f  d23 0000000000001000
    
    D/CrashAnrDetector( 3509):     d24 00000000000003f8  d25 0000000000000c08
    
    D/CrashAnrDetector( 3509):     d26 bf000000bf000000  d27 bf000000bf000000
    
    D/CrashAnrDetector( 3509):     d28 8000000080000000  d29 0000000000000001
    
    D/CrashAnrDetector( 3509):     d30 8000000000000003  d31 0000000000000008
    
    D/CrashAnrDetector( 3509):     scr 20000013
    
    D/CrashAnrDetector( 3509): 
    
    D/CrashAnrDetector( 3509): backtrace:
    
    D/CrashAnrDetector( 3509):     #00 pc 0010a4d0  /data/app/com.oculusvr.comawakes-1/lib/arm/libunity.so
    
    D/CrashAnrDetector( 3509):     #01 pc 003f8ec8  /data/app/com.oculusvr.comawakes-1/lib/arm/libunity.so
    
    D/CrashAnrDetector( 3509):     #02 pc 00016bbb  /system/lib/libc.so (__pthread_start(void*)+30)
    
    D/CrashAnrDetector( 3509):     #03 pc 00014c83  /system/lib/libc.so (__start_thread+6)
    
    D/CrashAnrDetector( 3509): 
    
    D/CrashAnrDetector( 3509): stack:
    

    Please help!
  • chrispruettchrispruett Posts: 200 Oculus Staff
    Are you compiling against the latest version of the mobile SDK? Sounds like you might be a version or two back. Entitlements were changed from opt-out to opt-in in the latest, and this looks like an entitlement failure.
  • dletozeundletozeun Posts: 26
    Hello Chris, thank you for your response. I am working with Unity 4.6.3p3 and Mobile SDK 0.4.3.1 which was the configuration that fixed all our crashing at start up / no stereo issues a while ago.

    I have seen the SDK 0.5.0 and 0.5.1 releases but I was not sure it would be safe to upgrade to the latest version seeing other having issues with these on Unity 5. Could you confirm I can safely upgrade my project with the 0.5.1 sdk ?

    Thank you very much for your time.
  • branditosonbranditoson Posts: 60
    Upgrading to the latest SDK version should be safe. If you don't want to try that, here's how you disable the entitlement check (for Unity builds):

    Select Edit > Project Settings > Player.
    In the PlayerSettings window, select the Android icon and expand the Other Settings tab.
    In the Scripting Define Symbols field, remove USE_ENTITLEMENT_CHECK if present.
  • dletozeundletozeun Posts: 26
    Upgrading to the latest SDK version should be safe. If you don't want to try that, here's how you disable the entitlement check (for Unity builds):

    Select Edit > Project Settings > Player.
    In the PlayerSettings window, select the Android icon and expand the Other Settings tab.
    In the Scripting Define Symbols field, remove USE_ENTITLEMENT_CHECK if present.

    Yes it is the first thing I did, following the challenge guidelines received by email. Actually, in my project there was already nothing in the "Scripting Define Symbols" field so this is not the cause of the problem.

    I am in the process of integrating the Mobile SDK 0.5.1 and building with it. I'll notify here how it is going on as soon as the build is ready and signed.
  • dletozeundletozeun Posts: 26
    My apk rebuilt on Unity 4.6.3p3 with ovr mobile sdk 0.5.1 is up and running fine now :) !

    Thank you very much for your quick support !
Sign In or Register to comment.