Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
Rwkeith's avatar
Rwkeith
Explorer
5 years ago

Unity Quest Build not loading (related to AndroidManifest.xml)

Hello, I've been configuring Unity and a new project for the quest.  I've noticed that if I don't Create a Store-compatible AndroidManifest.xml, the build loads and runs.  However, once I create it, my build just hangs with the Unity loading default screen even though the build is successful.  Removing it, allows my build to run on the Quest.  Am I not supposed to generate an AndroidManifest.xml unless/until I deploy to the store? 

I am hoping this will help me solve my root problem with my project seemingly having no Antialiasing whatsoever, even though I have it configured correctly to 4x AA under Rendering for android in the appropriate quality setting.

Thanks for your help!

2 Replies

  • Rwkeith's avatar
    Rwkeith
    Explorer
    5 years ago
    Okay, so this explains a bit more:

    DeploymentOperationFailedException: No activity in the manifest with action MAIN and category LAUNCHER. Try launching the application manually on the device.

    There shouldn't be a reason that I need to manually modify the AndroidManifest file, so what could be the cause of this error?


  • Rwkeith's avatar
    Rwkeith
    Explorer
    5 years ago
    My manfiests:
    <?xml version="1.0" encoding="utf-8" standalone="no"?>
    <manifest xmlns:android="schemas.android.com/apk/res/android" android:installLocation="auto">
      <application android:label="@string/app_name" android:icon="@mipmap/app_icon" android:allowBackup="false">
        <activity android:theme="@android:style/Theme.Black.NoTitleBar.Fullscreen" android:configChanges="locale|fontScale|keyboard|keyboardHidden|mcc|mnc|navigation|orientation|screenLayout|screenSize|smallestScreenSize|touchscreen|uiMode" android:launchMode="singleTask" android:name="com.unity3d.player.UnityPlayerActivity" android:excludeFromRecents="true">
          <intent-filter>
            <action android:name="android.intent.action.MAIN" />
            <category android:name="android.intent.category.INFO" />
          </intent-filter>
          <meta-data android:name="com.oculus.vr.focusaware" android:value="true" />
        </activity>
        <meta-data android:name="unityplayer.SkipPermissionsDialog" android:value="false" />
        <meta-data android:name="com.samsung.android.vr.application.mode" android:value="vr_only" />
      </application>
      <uses-feature android:name="android.hardware.vr.headtracking" android:version="1" android:required="true" />
    </manifest>

    It worked again after modifying the manifest to this::
    1. <?xml version="1.0" encoding="utf-8" standalone="no"?>
    2. <manifest xmlns:android="schemas.android.com/apk/res/android"
    3.     android:installLocation="auto">
    4.     <application
    5.         android:label="@string/app_name"
    6.         android:icon="@mipmap/app_icon">
    7.         <activity
    8.             android:theme="@android:style/Theme.Black.NoTitleBar.Fullscreen"
    9.             android:configChanges="locale|fontScale|keyboard|keyboardHidden|mcc|mnc|navigation|orientation|screenLayout|screenSize|smallestScreenSize|touchscreen|uiMode"
    10.             android:launchMode="singleTask"
    11.             android:name="com.unity3d.player.UnityPlayerActivity"
    12.             android:excludeFromRecents="true">
    13.             <intent-filter>
    14.                 <action android:name="android.intent.action.MAIN"/>
    15.                 <category android:name="android.intent.category.LAUNCHER"/>
    16.             </intent-filter>
    17.         </activity>
    18.         <meta-data android:name="unityplayer.SkipPermissionsDialog" android:value="false" />
    19.         <meta-data android:name="com.samsung.android.vr.application.mode" android:value="vr_only"/>
    20.     </application>
    21. </manifest>