[Bug] Invalid mainTemplate.gradle for Unity 6000.0 about firebase-unity-sdk

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[argzdev]

Hey @runette, the ndkVersion "**NDKVERSION**" should already exists within the mainTemplate.gradle once the project is created. Not sure how it's missing in your gradle file.

Running Force Resolve should rectify this problem. There shouldn't be a need to manually edit this.

[runette]

Hey @runette, the ndkVersion "**NDKVERSION**" should already exists within the mainTemplate.gradle once the project is created. Not sure how it's missing in your gradle file.

As you can see from the relevant file from the Test Application I created for the other issue #1025 - The file created by the SDK in this project which was a clean build and I accepted all of the defaults - did not have that line

https://github.com/runette/Firebase_Test/blob/master/Assets/Plugins/Android/mainTemplate.gradle

[runette]

Although - weirdly - the mainTemplate.gradle.backup file - that I think is created by the process that updates out of date entries in mainTemplate (e.g. compileSdkVersion => compileSdk ) DOES have that line. I am not sure if that process is yours or Unity's ?

https://github.com/runette/Firebase_Test/blob/6000/Assets/Plugins/Android/mainTemplate.gradle.backup

It looks a bit like edm4u has updated the entry and that other process has deleted it ??

[runette]

I did try deleting that line from mainTemplate.gradle and then running Force Resolve and it did nothing.

[argzdev]

That's really odd, let me do some more testing. Not sure if this is going to do anything different, but what happens if you delete the mainTemplate.gradle entirely then run Force Resolve? Somehow I think the Force Resolve might not be triggering for some reason.

[runette]

I deleted all of the gradle files and ran Force Resolve and no joy but then I built the app and the correct (except for the problems in #1025 ) file was created.

I am going to close this bug - since my feeling is that the problem is Unity related and the fix is to delete the files.