Random before/after-hook unknown error

[Brad7711]

By submitting this issue you are acknowledging that any information regarding this issue will be publicly available.

If you have privacy concerns, please email conformance-tools@fidoalliance.org

FIRST PRE CHECK

The documentation marked as TODO.

• [X] I SOLEMNLY SWEAR THAT I HAVE SEARCHED DOCUMENTATION AND WAS NOT ABLE TO RESOLVE MY ISSUE

What protocol are you implementing?

• [ ] FIDO2 Server
• [ ] CTAP2.0
• [ ] CTAP2.1
• [X] UAF 1.1
• [ ] U2F 1.1
• [ ] U2F 1.2

NOTE: UAF 1.0 certification have been officially sunset. U2F 1.2 only supported version of U2F.

What is your implementation class?

• [ ] Security Key / FIDO2 / U2F authenticators
• [ ] Server
• [X] UAF Client-ASM-Authenticator combo
• [ ] UAF Client
• [ ] UAF ASM-Authenticator

If you are platform authenticator vendor, please email conformance-tools@fidoalliance.org

What is the version of the tool are you using?

V1.6.2

What is the OS and the version are you running?

For desktop tools

• [ ] OSX
• [ ] Windows
• [ ] Linux

For UAF mobile tools

• [X] iOS 14.7.1 & 16.1.1
• [ ] Android

Issue description

• The error code 255 which happened in before-hook or after-hook appeared randomly.
• Could happen in any test cases at registration, deregistration or authentication.
• All the responses were recorded in our Client-ASM-Authenticator app, and they seemed correct yet got unknown error 255.

Screenshots

Related issues

#674

[yackermann]

@Brad7711 seems like your app returns error during pre-registration. Check app log

[Brad7711]

@herrjemand

Thank you for replying.

We have checked all the messages between the conformance tool and our app, and it seemed fine. It happens randomly, and sometimes there is no error at all (no failure, all pass). The 255 error code is only returned by our app when the key 'fail_if_unknown' is set. However, the tool showed 255 even if our app returned the error other than 255, e.g., 0, 6, etc.