[ad_1]
I’m implementing app attestation for my iOS app. That is my circulate:
- Registration
- Signing
I seen that generateAssertion doesn’t throw any error for a couple of days after registration was profitable. However then it begins throwing invalidKey error for a similar attestationKey.
From the outline of that error:
You obtain this error if one thing goes incorrect with producing, retrieving, or utilizing an App Attest cryptographic key, when:
- You name attestKey(_:clientDataHash:completionHandler:) for a key that’s already been attested.
- You name generateAssertion(_:clientDataHash:completionHandler:) with an unattested key.
- The App Attest service rejects the important thing.
Based mostly on my evaluation to this point, I’ve 2 query:
- I’ve already attested the important thing once I registered. Do I’ve to name attestKey once more after a couple of days and re-register?
- Is it motive 3 and the way will I do know why app attest service rejects the important thing?
[ad_2]
