Thanks for your reply and your answer is very helpful. Can I understand that my app has enabled Keychain sharing in signing and capabilities and my code not set kSecAttrSynchronizable. So the data I added using SecItemAdd during device to device transfer (e.g. using Quick Start) will not be sync or migrate？

Thanks for your reply and is very helpful for me. Can I understand that my app has enabled Keychain sharing in "signing and capabilities" and my code does not set kSecAttrSynchronizable. So the data I added using SecItemAdd will not be migrate or sync during device to device transfer (e.g. using Quick Start)?

Thanks for your reply and is very helpful for me. Can I understand that my app has enabled Keychain sharing in "signing and capabilities" and my code does not set kSecAttrSynchronizable. So the data I added using SecItemAdd will not be migrate or sync during device to device transfer (e.g. using Quick Start)?

Thanks for your reply and is very helpful for me. Can I understand that my app has enabled Keychain sharing in "signing and capabilities" and my code does not set kSecAttrSynchronizable. So the data I added using SecItemAdd will not be migrate or sync during device to device transfer (e.g. using Quick Start)?

Thanks for your reply and is very helpful for me. Can I understand that my app has enabled Keychain sharing in "signing and capabilities" and my code does not set kSecAttrSynchronizable. So the data I added using SecItemAdd will not be migrate or sync during device to device transfer (e.g. using Quick Start)?

Thanks for your reply and is very helpful for me. Can I understand that my app has enabled Keychain sharing in "signing and capabilities" and my code does not set kSecAttrSynchronizable. So the data I added using SecItemAdd will not be migrate or sync during device to device transfer (e.g. using Quick Start)?