Max Goedjen

@zachriggle @webtoolbox thanks for clarifying :) That UI is entirely provided by the system, I don't _THINK_ there's anyway to do that. Just out of curiosity, what's your use case?

So this _is_ technically possible by passing [.biometryAny](https://developer.apple.com/documentation/security/secaccesscontrolcreateflags/2937191-biometryany) here https://github.com/maxgoedjen/secretive/blob/a1009d0dacb63d19c522ba1cb555f0399081c017/Sources/Packages/Sources/SecureEnclaveSecretKit/SecureEnclaveStore.swift#L38 I'll consider adding this as a creation option in the future.

Basically my reservation is this: Users can use their password to remove/add Touch ID sets, which kinda makes the protection moot. There _is_ an option called [.biometryCurrentSet](https://developer.apple.com/documentation/security/secaccesscontrolcreateflags/2937192-biometrycurrentset) which would prevent...

> I would be fine with it removing the item if a Touch ID finger is added or removed. Main concern is that it's not really something I could adequately...

> It would be very useful to me if this could be added as an option for existing items as well though. That is almost definitely not possible, it's an...

I'll leave the ticket open for now while I give it some more thought. I could certainly see legitimate use cases for it, but need to weigh that against risks.

@PBHDK yeah, that's it – any time you see Sendability mentioned that's related to this, not anything wrong with your toolchain.

@PBHDK for the moment, you can turn down the concurrency warnings – there's a few in Xcode settings, and a few in the package. Try setting them to "minimal" or...

@robinMcA there's unfortunately some specific issue around updating that causes this that I haven't been able to pin down yet. Doesn't reproduce in a VM when that upgrades :/

@PBHDK I appreciate the offer and interest but I'd ask that you hold off on this for now – I'm not sure I'd be comfortable merging this yet for a...