Forum Discussion
Does Unity generate correct AndroidManifest.xml?
I am using Unity 5.3.2f1 on OSX 10.10.5. I've got "Virtual Reality Supported" option checked and I am able to run app on the device. However, after using check_submission script and generating release...
Yes, it looks like we need to make a couple of changes to Unity's output in order to produce a manifest that the store can ingest:
APK is launchable:
This is what needs to change:
<category android:name="android.intent.category.LAUNCHER" />
To:
<category android:name="android.intent.category.INFO" />
Exclude from Recents (android:excludeFromRecents) must be non-0 in manifest:
android:excludeFromRecents="true" needs to be added to the activity block.
I'm not sure why it's reporting a stale mobile SDK. 5.3.2f1 uses mobile SDK 1.0. Please let me know if that persists after the above changes. We'll work with Unity to make the above easier for shipping builds.
APK is launchable:
This is what needs to change:
<category android:name="android.intent.category.LAUNCHER" />
To:
<category android:name="android.intent.category.INFO" />
Exclude from Recents (android:excludeFromRecents) must be non-0 in manifest:
android:excludeFromRecents="true" needs to be added to the activity block.
I'm not sure why it's reporting a stale mobile SDK. 5.3.2f1 uses mobile SDK 1.0. Please let me know if that persists after the above changes. We'll work with Unity to make the above easier for shipping builds.