Correct - and sure thing. 
Iāve popped a link to a ZIP file of the stripped back project (sans Library & Builds folders) below. Iāve had one of my coworkers make a build from this same ZIP file and he was able to repro the bug with it, so hopefully itāll be the same for your developers.
https://drive.google.com/file/d/1M_qEPhKKxvJQL5XewB2TDa_SJ0PMP4YG/view?usp=drive_link
Hi Jess,
I have an update for you. The issue is still being looked into but it looks like weāve been able to narrow it down to the image library not being created with Lightship + ARCore. The cause is still something thatās being investigated since it doesnāt appear to be happening to every user. Can you try the following steps to see if it works for you as a workaround:
"com.unity.xr.arcore" entry in Packages/manifest.json to "5.1.4"Library folder to force a reimport of packagesGoogle ARCore as Android provider in XR Plugin ManagementThe purpose of the last two steps is to see if switching to ARCore without having to uninstall Lightship to do so will properly create the image library and then allow Lightship to use that same image library when building with Lightship
Thanks for the update! Iāve just followed those steps in the non-stripped back project, and tried a few other things. Unfortunately, still no luck. Here are my findings:
When I build with either provider, even if Iām not referencing Unityās provided TestReferenceLibrary in the project, I get this warning message:
When I build my test scene using that TestReferenceLibrary with either provider, the Debug Logs tell me that the image count is 0 (despite being able to see them set in Editor). (The logs say the count is as expected on my own TrackedImageLibraries when tested with each provider)
Also: I never have any issues deleting the Library folder before doing a Lightship + ARCore build, but after doing a Lightship + ARCore build I have to force delete (Shift + Del) the Library folder despite being on an Admin account. Even hitting continue and entering Admin credentials doesnāt let me delete it.
Iām in my last couple of days with our company, so my coworker @James_Brooks will be your point of contact on this bug report going forward.
James has just managed to get Image Tracking working in the following dev environment (with a caveat, see 
):
Enabled BOTH AR Core & Lightship + AR Core at the same time (which I know isnāt meant to be possible). When I had both providers checked in the ARDK3 beta it broke Semantic Segmentation & Occlusion Extension (see Discord ), so James is now testing to see if our must-have Lightship features are working with these settings. Heāll keep you updated on how this goes, cuz this might be an okay workaround for us in the interim. Hi Jess,
Thanks for letting me know. Itās been a pleasure interacting with you on our community forums and Discord. I wish you the best in your future endeavors
Iām not sure which of you will see this and reply back but what appears to be happening when both are selected is only ARCore is actually taking effect which is also the Lightship features such as semantics and occlusion extension stop working; ARCore completely overwrites Lightship.
Another thing that was suggested was maybe trying to rename the image library asset from its default name in case thatās somehow being used as some sort of magic hardcoded string value somewhere and itās causing issues
This may also be helpful. A user is having similar issues but in their case, they can remove ARCore after following the steps they provided in their last reply and it seemed to work. Itās similar to what I originally suggested just in a bit of a different order. https://community.nianticspatial.com/t/ardk-3-6-stops-image-tracking-from-working/4659/3
Hi Jesus,
Thank you for the update. I will be picking up on this where Jess has left off. First of all thank you so much for taking the time to go through this with her and helping us with this bug. Iāve had a speed-walk through with Jess as she has obviously been the one handling the work weāve been doing with ARDK.
As Jess mentioned, I had previously been able to check both ARCore and Lightship boxes, but that is no longer the case as selecting the Lightship box disables the ARCore one now.
I will take a look through the link and then walk through before testing again.
Hi James,
Checking in to see if you had a chance to try out the userās solution I linked
Hi Jesus,
Sorry for delay, comms were down for a bit last week.
So yes, I was able to try that solution that worked for the other user but without any luck. As Jess had mentioned previously I was able to have both ARCore and the Lightship + ARCore boxes ticked, but that didnāt last long as closing and re-opening Unity mustāve reset the loaders and I could no longer check the ARCore box.
Also, having the Lightship + ARCore box ticked now results in me having black screens on my AR scenes, and I no longer get a permission to use Camera popup? When I remove Lightship from the project and use ARCore separately thatās not an issue.
I am also targeting API 34 now and wondered if this could be an issue?
Just wondering if there has been on progress on this bug or if there is anything else we could possibly try?
Hi James,
Iām sorry about the delay. I hadnāt heard back and lost track of this topic.
Ok so then if what that user proposed didnāt work for you, let me check on the status of the bug I filed
Any update on the status of this bug?
There hasnāt been any change in the behaviour. Still using ARDK 3.6, but I see there is a more recent version at 3.7.
I suppose upgrading to this version couldnāt do any harm and keep trying.
Hi James,
I would recommend updating to 3.7 if thatās something you can do. Weāre still looking into the issue. At the moment we believe itās a versioning issue but havenāt been able to determine which version of what is causing problems with image tracking.
Hi Jesus,
Thank you for that response. Okay, I will strip out 3.6 and anything else that came with it, and install 3.7 to see how we go. Fingers crossed some kind of magic happens
