Skip to main content
Anonymous
January 4, 2023

ovr upload fails due to missing android exported in manifest

I started receiving the following failures from ovr-platform-util when uploading quest apks with multiple apps and no changes to my manifest file:

The AndroidManifest.xml contains an <intent-filter>, but android:exported was not set on its parent node. Add it to your manifest and try again. See https://developer.android.com/about/versions/12/behavior-changes-12#exported for more details.
 
Anyone else experiencing this ?

    4 replies

    CritterHP5
    CritterHP5
    Inspiring
    June 21, 2023

    Got this error after setting the target sdk to 32.

     

    Update

    Console output pointed to this page

    https://developer.android.com/about/versions/12/behavior-changes-12#exported

    I used apktool to decompile/compile the apk and updated the manifest by adding android:exported="false" to parent components that contain an intent filter element and was able to bypass the error. Just gotta figure out how to sign/align apk. Not sure if any issues with this method.

    Update - got a build to upload and run. For the queries tag, exported = true. For the activity tag exported = true. If I used false, the app would build and upload but wouldn't launch. Used apktool to decompile and compile, zipalign to align, and apksigner to sign.


    Update - Alternative solution; UE4 Project Settings > Extra Tags for UE4 Game Activity <activity> node

    • android:exported="true"
    • Didn't need to create a ManifestRequirementAdditions.txt with a copy of the queries block with android:exported. Also, it removed the android:exported property from it anyway.
      DubFitness
      Participant
      August 30, 2023

      After setting the target sdk to 32 I can't package or launch from the editor.  I added android:exported="true" to Activity Extra Tags and now I can package but still can't launch from editor.  I get blank screen and the game never starts.  I am afraid to make the APK live if I can't even get it to launch from editor.   Wish I didn't have to spend time dealing with this, the mandated Target SDK 32 changes has cost me 2 days and counting.

      tangjunlong
      Up and Coming
      December 23, 2023

      I also encountered this black screen problem, and then installed the apk to my quest1 through packaging instead of startup, and then it started successfully

      Terms & ConditionsAccessibility statement