Post marked as solved
Click to stop watching this thread.
You have stopped watching this post. Click to start watching again.
contentPostList.repliessolved.tooltip
Thank you for the quick response, Quinn.
We will collect sysdiagnose logs from the customer's device in the coming weeks and file a DTS tech support incident with that data.
In the meantime, can you please provide any more insight about the scenarios you expect the SecKeyCreateSignature(…) function to return the CryptoTokenKit -3 error (TKErrorCodeCorruptedData) with message "<sepk:p256 kid=1214c04d05261ee3>: unable to sign digest"? Also, is the "corruption" terminology referring to the dataToSign input to SecKeyCreateSignature(…), or is it referring to a different kind of data corruption? Any additional information here would be helpful for us to investigate and potentially redesign the system around.
Unfortunately re-enrolling via key deletion and recreation is not currently a tenable solution for this app, in which the Secure Enclave private key signing has an essential role.