Errors with Attestation on App

Question

Created Apr ’25

Replies 3

Boosts 0

Participants 2

We recently deployed Attestation on our application, and for a majority of the 40,000 users it works well. We have about six customers who are failing attestation. In digging through debug logs, we're seeing this error "iOS assertion verification failed. Unauthorized access attempted." We're assuming that the UUID is blocked somehow on Apple side but we're stumped as to why. We had a customer come in and we could look at the phone, and best we can tell it's just a generic phone with no jailbroken or any malicious apps. How can we determine if the UUID is blocked?

Boost

Answer 1

Engineer OP

Apple

Apr ’25

Who is printing this error? It is not coming from the DeviceCheck/AppAttest framework.

If you are printing this error in your app yourself, what is the actual error condition that triggers this? What is the error you are getting from the API or the service?

If your code is not printing this error, you will want to check if any 3rd party libraries you might be using is doing so. In that case, you may want to check with them and find out what the root cause for this is, what is the actual API or service error triggering this.

If the root cause error is coming from the API please share the complete error code and message. If it is coming from the App Attest service, then share the complete error message you are getting returned, including the status code and the text error.

0

Answer 2

Engineer OP

Apple

May ’25

Also, do check with these customers to see if the issue is now fixed. We encountered a network issue that was returning errors in some regions

0

Answer 3

star3132 OP

May ’25

Thanks for letting me know about the network issue with regions... would this affect a certain device always failing attestation? Also, is there anyway to get more information about why a device is failing attestation?

0