feat(verifier): require SDK Tethering in iOS/Android verifier sample apps#303
Merged
Conversation
… apps Update the in-person and remote verification sample apps for the Verifier SDK breaking changes (iOS Verifier 6.0.0, Android 7.0.0). React Native and web verifier apps are out of scope for this change. In-person (proximity): - android: initialize with a PlatformConfiguration (tenantHost + applicationId), handle FailedToRegister/InvalidLicense, bump verifier dependency to 7.0.0, treat MobileCredentialResponse.credentials/.credentialErrors as non-null - ios: async initialize with PlatformConfiguration + tethering error handling, add tenantHost/applicationId constants, rename verificationResult.reason to .failureType Remote (app-to-app / OID4VP): - android: supply applicationId via PlatformConfiguration (removed from requestMobileCredentials), handle the new sealed OnlinePresentationSessionResult (Success/Failure), tethering error handling, bump verifier dependency to 7.0.0 - ios: applicationId via PlatformConfiguration (removed from requestMobileCredentials), async initialize, rename .reason to .failureType
…ote sample From iOS Verifier SDK v6.0.0, OnlinePresentationSessionResult is a @Frozen enum with success(sessionId:challenge:mobileCredentialResponse:) and failure(sessionId:challenge:error:) cases. Replace the old nullable struct-property access with switch/case, matching the Android sample and the v6.0.0 migration guide.
dylan-paul
approved these changes
Jun 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates the in-person and remote (app-to-app) verifier sample apps for the Verifier SDK breaking changes shipped in iOS Verifier SDK v6.0.0 and Android Verifier SDK v7.0.0, the headline being that SDK Tethering is now required.
Companion to the MATTR Learn PR mattrinternal/mattr-learn#789, which documents the same migration. React Native and web verifier sample apps are intentionally out of scope (the React Native Verifier SDK is not tethered).
Changes
In-person (proximity)
android-in-person-verifier-tutorial-sample-app): initialize with aPlatformConfiguration(tenantHost+applicationId); handle the newFailedToRegisterException/InvalidLicenseException; treatMobileCredentialResponse.credentials/.credentialErrorsas non-null lists; bumpglobal.mattr.mobilecredential:verifierto7.0.0.ios-in-person-verifier-tutorial-sample-app):initializeis now async and takes aPlatformConfiguration; addtenantHost/applicationIdconstants; handlefailedToRegister/invalidLicense; renameverificationResult.reason→.failureType.Remote (app-to-app / OID4VP)
android-remote-verification-tutorial-sample-app): supplyapplicationIdviaPlatformConfiguration(removed fromrequestMobileCredentials); handle the now-sealedOnlinePresentationSessionResult(Success/Failure) withwhen/is; tethering error handling; bump verifier to7.0.0.ios-remote-verification-tutorial-sample-app):applicationIdviaPlatformConfiguration(removed fromrequestMobileCredentials); asyncinitialize; rename.reason→.failureType.Notes
https://your-tenant.vii.mattr.global/<YOUR_VERIFIER_APPLICATION_ID>) for developers to fill in, consistent with the existing sample-app conventions.devbranches. Builds were not run locally as the SDK distributions are added out of band per each app's README.🤖 Generated with Claude Code