Quest build suddenly removing android.intent.category.LAUNCHER

Hello,

For some reason, after I build now, I'm not longer able to launch apps via adb. I have this in Plugins/AndroidManifest.xml:

Code (CSharp):

1.       <intent-filter>
2.         <action android:name="android.intent.action.MAIN" />
3.         <category android:name="android.intent.category.LAUNCHER" />
4.         <category android:name="android.intent.category.LEANBACK_LAUNCHER" />
5.       </intent-filter>

But looking at the apk in Android Studio's Analyze APK, I only see:

Code (CSharp):

1.             <intent-filter>
2.                 <action android:name="android.intent.action.MAIN" />
3.                 <category android:name="android.intent.category.INFO" />
4.             </intent-filter>

This has worked fine in the past, and I don't think there have been any other manifest changes. I did move from 2019.2 to 2019.4.10f1 recently, but I don't know for sure if this broke before of after that transition.

Anyone else seeing this? Any thoughts on what could have changed?

Thanks!

 

Hello! I'm running LegacyVR in 2019.4.10f1.

 

That's encouraging, I'm hoping it's just something on my end that I can tweak - I just can't yet find anything that has changed on my end other than moving to 2019.4.10.

Question: Were you testing with LegacyVR or only with XR Plugin Management?

Yes - both of those are true.

I will try to do some small scale tests to see if I can replicate it as it would be difficult to submit this large project. I'm encouraged to hear this is not intended behavior.

Thanks for your time!

 

Update: after a lot more digging, this is coming from the Oculus Integration 20.0, dated Sep 3, 2020. In addition to moving forward on Unity, I'd also recently updated the Oculus Integration SDK as well.

Specifically, it comes from OVRGradleGeneration.cs OnPostGenerateGradleAndroidProject, which ends up calling:

Code (CSharp):

1. OVRManifestPreprocessor.PatchAndroidManifest(file, enableSecurity: patchedSecurityConfig);

That method, among other actions, specifically removes those categories from my custom AndroidManifest file when building. I get that you would want to do that for store submission manifests, but it seems odd that there is no ability to leave that alone for testing.

Anyway, easy enough to comment out, just frustrating.