No Manifest File

You can grab the version Unity creates, modify it and copy it into the right asset folder. It gets created in a build subdirectory of the project (can't remember the exact name) when unity does an Android build.

Ah great, So check "Google Android Project" which creates a Manifest file i can drag into my Plugins Folder, and then uncheck  "Google Android Project" and revert to building an APK?

I'm not sure which check you're referring to (don't have my project on this computer so can't check). I built an APK in every instance though and it will include a manifest every time. Unity will use an existing manifest file and amend it as needed (in my project it adds some more permissions), so you build once, copy the manifest, edit it, save it in plugins, then build again.

The generated one is in Temp/StagingArea.

When i check "Google Android Project" it dumps a Manifest file in the main folder, but no APK. This is the first Android title we have released so just wading through all the knowledge bases to get up to speed.

When I create an APK how do i find the Manifest file inside, as its only one file? 

I didn't pull the manifest from the APK, I got it from Temp/StagingArea after Unity built the APK. I'm guess I have "Google Android Project" off in that case.

When you build your project (say it's called MyProject) and it produces and APK, is there a directory MyProject/Temp/StagingArea?

I believe it's possible to pull the manifest from the APK but I don't know how to do it.

No, when I build the project I simply get an APK file with no extra folders. Ive got the AndroidManifest inside the Plugins/Android/assets folder, but im not 100% sure its being referenced correctly as some of the submission test errors clearly have been resolved in the Manifest, but the errors are still showing.

head scratch...

Ive also checked in the project folder (with show hidden folders enabled) and there is no Temp folder.

Unity auto-generates the AndroidManifest based on your project settings. It also tries to merge any AndroidManifest you provide into the generated version. @Fulby is describing the location of the generated AndroidManifest.

> im not 100% sure its being referenced correctly as some of the submission test errors clearly have been resolved in the Manifest, but the errors are still showing.

What errors? How did you fix them? If your project includes a file Assets/Plugins/Android/AndroidManifest.xml, Unity should merge any XML elements that don't conflict with its built-in settings.

Ok, So, I did a build and left Unity open and ive now found the AndroidManifest.xml in the temp folder.

It looks identical to the one I placed in the Plugins/Android folder so I seem to be on the correct track.

Main issue is im getting errors that i know i have resolved in the Manifest.
APK Is launchable ( <category android:name="android.intent.category.INFO" />)
GLES Version is not specified (  <uses-feature android:glEsVersion="0x00030000" android:required="true" />)

Any ides why im getting the errors when the manifest is edited correctly?

EDIT: 4 Errors Down - Only 1 to go!

Im still getting the GLES warning. Manifest reads - <uses-feature android:glEsVersion="0x00030000" android:required="true" />

Graphics API is set to OpenGLES3 in Unity as this seemed to solve poor performance on the S7, and still works perfectly on older devices (Note 5, S6 etc)