Got it. Ok let me take some time to repro this and get back to you. I recall having run into this in the past but I don’t think it was blocking me from building. I’ll keep you posted.
Could you share screenshots and maybe a video of the build process on your end. I see the message that you’re getting; I’m getting a similar message as well but it’s not an error it’s a warning which should not be blocking the build process.
Are you using our samples package and/or using a sample as a base for your project or is this a project you’ve created completely from scratch using NSDK? May I also know what AR features and components you’re currently using in your project?
Also, can you check the Project Validation tab and make sure everything there is set accordingly? It can be accessed via the NSDK tab on the top menu bar in Unity.
Since I am familiar with ARDK3, I just created this new ARDK4 project from scratch two days ago, it could be compiled on a windows machine. Then yesterday I copied it to my Mac and planned to have a look at the new VPS2 feature.
However, I followed the wrong instruction and kept using the ARLocationManager from VPS1. I just downloaded one scanned site from scaniverse. Then I imported it into the editor, getting the manifest file and prefab. And it did not compile successfully and these no meta file error appeared, if I remember it correctly.
This following screenshot includes the project validation panel, and hierarchy list of game object in the scene now. I have removed the manifest file, site prefab in the asset folder and all the VPS1-related components in the scene. Now it only includes the original AR session and XR origin. I also attached one primitive cube under XR origin for testing. I believe now it is just a hello-world AR application, without any NSDK dedicated feature.
I would suggest also removing the older 3.17 Location Manager and anything you did the old 3.x way since that sounds like it could be the source of the error.
I believe I may have found the solution. It seems that the reason those errors are appearing is that the README and LICENSE files were made in GitHub since that’s where the UPM is being hosted. When imported to Unity there is no meta file because the files were not created in Unity.
To get around this I did the following:
Open Unity Hub
Click the three dot menu all the way to the right of your project
Click on “Reveal in Finder” if you’re on Mac or “Show in Explorer” if you’re on Windows
Navigate to Library → PackageCache
Locate the Niantic Spatial package and cut and paste it into project root directory Packages folder
The reason you want to Cut and Paste is that you only want to have one of these packages not duplicates. If you’re not seeing options to cut the folder (I didn’t see one on Mac), copy it and make sure you delete it after copying and then paste it into the Packages folder.
If the project is already open, it will refresh when you bring it back to the foreground and the errors should be gone now.
I did notice this followed up with some warnings but none of those warnings appeared to be any real issues. Regardless I let our team that works on the packaging know about this.
