I was in a similar boat.  I was in a time crunch and just needed to get it up, it'd probably be easier to build a project from Unity instead (i didnt have access to the project at the time).  So this does work, if you'd rather do it this way.

1. Decode the apk with APKTool

2. Edit Manifest to remove arcore

3. Rebuild the apk

4. Resign the apk from the command line

5. zipalign using a value of 4

dpizzle wrote:

I was in a similar boat.  I was in a time crunch and just needed to get it up, it'd probably be easier to build a project from Unity instead (i didnt have access to the project at the time).  So this does work, if you'd rather do it this way.

1. Decode the apk with APKTool

2. Edit Manifest to remove arcore

3. Rebuild the apk

4. Resign the apk from the command line

5. zipalign using a value of 4

Vuforia support...what say you? Is this how we are supposed to submit a functional app using Vuforia to the play store?  If so, OMG! Not able to focus is non-functional,IMO. I have access to the Unity project, btw. 

Thanks dpizzle for the reply

There are some solutions here in regards to the manifest: https://developer.vuforia.com/forum/unity/play-store-submission-error-comgooglearcore

Seems like they are aware that editing the manifest might be necessary in this regard.



If you want to explore why the autofocus is not working. Maybe try using a newer version of ARCore, 1.4 is kinda old now.  

But if you don't need any ARCore functionality, you should probably just leave it out.

I cannot leave arcore out of the unity project because vuforia writes arcore tags inside the android manifest file inside the apk file,and when you upload to google play google will reject saying Hey where is the arcore library. Thats why vuforia says place the arcore library in the folder, but then vuforia cannot use autofocus anymore with the arcore library there. 

I'm trying to import the unity project into android studio and I'm getting gradle errors.Currently troubleshooting. 

Did you happen to try that technique from that thread?  I'm curious if Vuforia will override and write tags into a user provided manifest.  If that doesn't work, I guess you'll have to use an Android Studio project or decode/recode the apk.  That wasn't too hard, only took about 20 minutes to figure out and you could batch it for future.



 

I got it to work-build-publish...it was a pain.

Exported the project from Unity, followed this tut for importing into android studio: https://support.unity3d.com/hc/en-us/articles/115005695763-Exporting-a-project-to-Gradle-and-building-deploying-on-Android-Studio

up until the step about run configuration.

copied this into the original unmerged manifest xml file:

<meta-data android:name="com.google.ar.core.min_apk_version" android:value="24" />

    <meta-data android:name="com.google.ar.core" android:value="optional" />

immediately under the <application opening tag in the manifest.

generated a signed apk. published

vuforia writes arcore stuff into the merged manifest even when built from Android Studio (AS), so it is not only about building with AS! You have to edit the ORIGINAL un-merged manifest file also or Vurfuria puts its own meta tags into the merged manifest file in the build like so:

<meta-data

            android:name="com.google.android.gms.version"

            android:value="@integer/google_play_services_version" /> <!-- To support the ODG R7 in stereo mode we must add the following library. -->

<UNWANTED VUFORIA GENERATED ARCORE TAGS HERE>

 <uses-library

            android:name="com.osterhoutgroup.api.ext"

            android:required="false" />

This of course cause google to reject the apk because I did not include the aar file in the plugins folder of unity, BECAUSE IT KILLS FOCUSING! Not yelling at you...just venting a bit. All in all I'm good. It just takes extra work now to build and there is no out of the box solution.

I hope this post helps someone.

Hello,

Thanks for your patience with this issue. We realize it is a challenge to overcome, and apologize for the inconvenience.

I see activity on the ticket to resolve this issue, so I'm hopeful that it will be resolved in our next commercial release.

Keep you posted.

Thanks,

Vuforia Engine Support

Hello,

With Vuforia Engine 8.3, we've added a new configuration setting to specify whether ARCore is be required, optional, or not used at all in an Android application. This can be found in the DeviceTracker section of the Vuforia configuration.

Thanks,

Vuforia Engine Support

From the outset the self-adjust was effectively set in my application. Be that as it may, after installind ARCore and running my application again the self-adjust couldn't be set any longer. So by one way or another ARCore breaks the self-adjust in aboutall.