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...
Perhaps it's a different issue--more to do with Unity either overwriting or not recognizing the (correctly customized per your recommendations!) AndroidManifest.xml file I added. :shock:
Well, now I'm trying to build my signed APK for submission, and it gives me this error in the console:
Error building Player: XmlException: 'manifest' is expected
and then it lists the file path of the manifest file I added in my project under Assets/Plugins/Android/AndroidManifest.xml
It seems to be asking that I rename 'AndroidManifest.xml' to be 'manifest.xml' but when I rename it as such, Unity overwrites it with the default manifest. What is up with this error?
Your Validator tool is super helpful, btw! Before switching out my osig file for my own key, I got my build down to 1 error: 'Certificate is a debug cert'! So, this error with my custom manifest file is new...
As a last resort, I've been thinking about replacing the default Unity manifest file with my altered one and then switching it back, once I've built this thing. Is that a bad idea?
Let me know if you guys need more info on this situation--I'm pretty stumped on this end. :?
Thanks again!
p.s. Maybe it's an issue with plugins I'm no longer using that are still in the Plugins directory, overwriting the manifest? ...will fiddle with this and report back.
<EDIT> The problem does not seem to be the plugins. I'm heading over to the Unity forums to ask about this, because it's more of a Unity issue!
Well, now I'm trying to build my signed APK for submission, and it gives me this error in the console:
Error building Player: XmlException: 'manifest' is expected
and then it lists the file path of the manifest file I added in my project under Assets/Plugins/Android/AndroidManifest.xml
It seems to be asking that I rename 'AndroidManifest.xml' to be 'manifest.xml' but when I rename it as such, Unity overwrites it with the default manifest. What is up with this error?
Your Validator tool is super helpful, btw! Before switching out my osig file for my own key, I got my build down to 1 error: 'Certificate is a debug cert'! So, this error with my custom manifest file is new...
As a last resort, I've been thinking about replacing the default Unity manifest file with my altered one and then switching it back, once I've built this thing. Is that a bad idea?
Let me know if you guys need more info on this situation--I'm pretty stumped on this end. :?
Thanks again!
p.s. Maybe it's an issue with plugins I'm no longer using that are still in the Plugins directory, overwriting the manifest? ...will fiddle with this and report back.
<EDIT> The problem does not seem to be the plugins. I'm heading over to the Unity forums to ask about this, because it's more of a Unity issue!