How did we do? We’d love to know your thoughts on this year’s conference. Take the survey here
Hello, Preparing to use the app attest service documentation suggests we call attestKey(_:clientDataHash:completionHandler:) fewer than 100 requests per second.
I had a question - Our app might theoretically hit this limit on launch. Would Apple be able to relax these limits or is this a hard limit?
This is a safe limit for you to avoid running into throttling and errors.
Apps with a large number of existing users should be careful about turning App Attest on all at once, and we recommend turning it on for users in small increments gradually. The key call that trigers contacting the servers and might cause throttling is attestKey(_:clientDataHash:completionHandler:). The servers might throttle the requests from an app if too many instances start making this request at the same time.
What is most important is to make sure you are only making one attestation request per app installation per device. Otherwise you risk multiplying the requests further, causing issues.
If and when you hit throtting, our guidance is to make sure you check for errors, and if you get a failed attestation, you would want to back off your requests and retry at a later time. Once you hit the throttle, and if you back off right away, it should not take long for the error to clear.
Please read how to Release a version update in phases
Argun Tekant / DTS Engineer / Core Technologies
Thank you for the detailed answer. You said it should not take long for the error to clear.. How much time is not long please?