Yes, they are very similar, but that's by design. What I'm trying to accomplish is to have a series of images which are identical on one side and different on the other side. I want them to match each other. So I took a series of photos. They all have the same stuffed animal on the left side, and different ones on the right side. Except for one image, which has no stuffed animal on the right side. The idea is that the image with one animal should match any of the ones with two. So the one with one animal is tracked, and the others are scanned. This actually works fine. I was testing and reversed which image was tracked and which was scanned, and that's when I noticed this behavior. It doesn't happen if both images have two stuffed animals.. they match in both directions. It only happens with the image that has only one. It won't interfere with what I'm trying to do, but the behavior didn't make any sense to me so I wanted to understand what's going on and if it's a sign that I'm doing something wrong.

I've been playing around with this a bit more. It turns out that I can use use didAdd instead of nodeFor if I don't set a position for the cube, and if I add it to the passed in node instead of the root node. Any other variation has the cube moving around to some degree. It also only holds still if I use an ARImageTrackingConfiguration. If I use a ARWorldTrackingConfiguration instead, which I believe should also work, the cube moves no matter what else I do. Why?

I have two versions of this code which both exhibit the same problem, one in SceneKit and one in RealityKit. For RealityKit, this code is called from session:didUpdate:. For SceneKit, it is called in renderer:nodeFor:. I added it to renderer:didUpdate just in case but it didn't help. I am using ARImageTrackngConfiguration in both, and I have set maximumNumberOfTrackedImages to 1. I can share the whole file if you would like... just let me know if you want to see SceneKit, RealityKit, or both. Thanks for your help!

I have discovered that the minimum length to create a signature is 1 second, but so far I haven't been able to get anything shorter than 2.5 seconds to be recognized by ShazamKit. Does this sound like an expected result?