yup docs are incorrect. for the start event, though if I passed just timestamp: 0 things worked fine for me.

I have two swift files. main.swift and other.swift. I compile them as such swiftc -emit-object main.swift other.swift Greet When I do: clang -o Greet main.o other.o I get: ld: warning: Could not find or use auto-linked library 'swiftFoundation' ld: warning: Could not find or use auto-linked library 'swiftDarwin' <removed for brevity> ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1  Can you tell what's wrong?

Thanks I read the first link. It’s the former. I forgot to mention I’m aware or list-keychains. So this is obviously in the case that both of them are part of the search list. But often the locked item is found. we run into this situation because a jenkins build job may have not deleted a private/custom keychain or may have added a cert into the login keychain (which is against our instructions). And we shouldn’t be in this situation. I agree with the direction you’re guiding me. This was more a question to gain foundational knowledge on how keychain look ups work when identical name exists within the search filter. Helps me debug our potential Jenkins build agent problems