chore(react-native-verifier-tutorials): update for Verifier SDK 10.0.0 - #333
Merged
Merged
Conversation
Updates both React Native Verifier tutorial projects for the breaking changes in @mattrglobal/mobile-credential-verifier-react-native 10.0.0: - SDK Backend (tethering) is now required, so `initialize` takes a `platformConfiguration` with a tenant host and verifier application ID. This is new for the in-person project, which previously needed no tenant at all, so it gains a `Constants.ts` matching the remote project's. - `requestMobileCredentials` no longer takes `applicationId`; it uses the one supplied at initialization. - `OnlinePresentationSessionResult` is discriminated on `isSuccess` instead of carrying an optional `error`. - `getTrustedIssuerCertificates` now returns a `Result`, and `addTrustedIssuerCertificates` can now fail with `InvalidLicense`, so both are unwrapped rather than used directly. - `MobileCredentialResponse.credentials` and `credentialErrors` are required arrays, and `VerificationResult` is discriminated on `verified`, so `reason` is reached by narrowing rather than optional chaining. The lockfiles are deliberately untouched. They must be regenerated once 10.0.0 is published, which is also when this can first be typechecked.
dylan-paul
approved these changes
Sep 9, 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.
Updates both React Native Verifier tutorial projects for
@mattrglobal/mobile-credential-verifier-react-native10.0.0, which ships on 9 September 2026. Mirrors the Holder SDK 10.0.0 sample-app update.What changed
SDK Backend (tethering) is now required.
initializetakes aplatformConfigurationwith a tenant host and a verifier application ID, and can now fail withFailedToRegisterorInvalidLicense. This is the significant change for the in-person project, which previously calledinitialize()with no arguments and needed no MATTR VII tenant at all. It gains aConstants.tsmodelled on the remote project's, with per-platform application ID placeholders.Remote verification.
requestMobileCredentialsno longer takesapplicationId, andOnlinePresentationSessionResultis discriminated onisSuccessrather than carrying an optionalerror. The old comment inApp.tsxstating "There is noisSuccessflag" is now wrong and has been replaced.Both projects.
getTrustedIssuerCertificatesreturns aResult,addTrustedIssuerCertificatescan now fail withInvalidLicense,MobileCredentialResponse.credentialsandcredentialErrorsare required arrays, andVerificationResultis discriminated onverifiedsoreasonis reached by narrowing.All four
package.jsonfiles move from^9.0.1to^10.0.0. The two starter projects are blank scaffolds, so only their dependency changes.Not done here
The lockfiles are deliberately untouched, following the Holder 10.0.0 precedent. They can only be regenerated once 10.0.0 is on npm, which is also the first point at which these apps can be typechecked. There is no CI for the sample apps, so please treat a local
tscafter publication as the real gate.Related