Recommended lifecycle for prepared MobileDocumentReaderSession

Question

Created 23h

Replies 1

Boosts 0

Participants 2

This post is from the WWDC26 Wallet Q&A.

For high-throughput in-person ID Verifier flows, is it recommended to call MobileDocumentReader.prepare() before the operator starts a check and cache the prepared MobileDocumentReaderSession for one later requestDocument call?

Or should apps only call prepare() after explicit user intent? If prewarming is supported what should invalidate a prepared session?

Answer 1

Engineer OP

Apple

22h

Accepted Answer

Thank you for reaching out! We recommend you call MobileDocumentReader.prepare() before the operator starts a check because the operation may need to perform a network call. You may use the same session object to perform multiple read operations. You can invalidate the reader session by deallocating it. Please take a moment to review the Adopting the Verifier API in your iPhone app article.