"We offer new support options and therefor the forums are now in read-only mode! Please check out our Support Center for more information." - Vuforia Engine Team

AndroidManifest override and split application binary - Unity

By DevSonic on Wed, 09/12/2018 - 09:44

Hi,

I've been searching for a solution for 2 days but can't be able to find it. It starts with the build larger than 100MB so I enable the Split Application Binary (SAB) option. Then I try uploading it to the Play Store and get the error :

"The minimum version code of the ARCore dependency com.google.ar.core.min_apk_version is not in the AndroidManifest.xml file, but the com.google.ar.core metadata tag has been specified" (although I'm not using ARCore and ARCore Supported is NOT checked)

So I search and find that I can override the AndroidManifest to add the missing line, so I build, copy the AndroidManifest from "Temp/StagingArea/" folder to my "Plugins/Android/" folder, add the line and build again. Now I can upload the build to the Play Store (wait for it to be online) then when I launch the app it looks like the .obb can't be accessed. (I tried using the Apk without the .obb directly on my phone and I had the same issue)

I tried multiple things and think the problem is related to AndroidManifest override and SAB because if I don't split my app or if I don't override AndroidManifest the app is working fine. But then I can't upload it to Play Store, either it's too big, either I got the ARCore error and now I'm stuck. 

I think there are multiple ways to fix this but it used to work without overriding AndroidManifest so I guess its just the google.ar.core line being added when it should not or the min_apk_version line not being added when it should.

 

Hope I explained myself clearly and that we can find a quick solution together,

Best Regards

 

Hello DevSonic,

A user over in this thread, https://developer.vuforia.com/forum/unity/play-store-submission-error-comgooglearcore, seems to have found a solution to a problem that sounds very similar to yours. Could you try their suggestion and let us know if it fixes your issue?

Hey Strasza,

I haven't solved this problem yet and I need to have it working for next week (the sooner the better) so here are some additional infos if it can help you figure this out or find a workaround

I'm using Unity 2018.1.0f2 and Vuforia 7.2.23. 

Hello,

Can you confirm that when you override the manifest you are adding bot ARCore being optional AND setting the min APK version to 24? Both of these are required for that solution to work.

Hey,

 

First thanks for your answer.

Yes I added both lines as stated in my first post and the error on the play store was gone so I could publish the new app but the problem is the app launched isn't working properly.

 

Well after reinstalling Unity for another reason it happens that it got the older Vuforia version that I used to use. When I searched for an older version I couldn't find one recent enough so this was a good thing.

We found the solution. Do the manifest steps as you already have, but before you make a build, you need to remove a line in the manifest that says <meta-data android:name="unity.build-id" android:value="[some id]"/>.