Thanks for the updates. To follow up from our side: we are an SDK provider, and we cannot reproduce this issue locally unfortunately. Based on our production telemetry: It occurs most frequently during DCAppAttestService.shared.generateAssertion. Because generateAssertion runs locally on-device, this indicates a local system or state failure. It persists on the same devices over multiple days, meaning it does not self-recover over time. We are looking for guidance on how to recover from this state: Would clearing the stored key and regenerating a new one (generateKey + attestKey) unstick affected devices? Are there recommended steps for users/integrators, such as restarting the phone or updating the iOS version? If anyone has successfully resolved this in production, any insights would be appreciated.

Did you reach any conclusion on this one? We're also running into it but there is very limited documentation around DCError.unknownSystemFailure or the resolving of it.