Learn how to build an application that can verify an mDoc presented via a proximity workflow

• As part of your onboarding process you should have been provided with access to the following assets:
  • ZIP file which includes the required framework: (MobileCredentialVerifierSDK-*version*.xcframework.zip).
  • Sample Verifier app: You can use this app for reference as we work through this tutorial.

• As part of your onboarding process you should have been provided with access to the following assets:
  • ZIP files that include the required library (common-*version*.zip, verifier-*version*.zip).
  • Sample Verifier app: You can use this app for reference as we work through this tutorial.

• Xcode setup with either:
  • Local build settings if you are developing locally.
  • iOS developer account if you intend to publish your app.

• Android Studio.

• Verifier device:
  • Supported iOS device to run the built Verifier application on, setup with:
    • Bluetooth access.
    • Available internet connection.
• Holder device:
  • Mobile device with the MATTR GO Hold example app installed and setup with:
    • Biometric authentication.
    • Bluetooth access.
    • Available internet connection.

• Verifier device:
  • Supported Android device to run the built Verifier application on, setup with:
    • Bluetooth access.
    • Available internet connection.
    • USB debugging enabled.
• Holder device:
  • Mobile device with the MATTR GO Hold example app installed and setup with:
    • Biometric authentication.
    • Bluetooth access.
    • Available internet connection.

Step 1: Create a new project

Please follow the detailed instructions to Create a new Xcode Project and add your organization's identifier.

Step 2: Unzip the dependencies file

1. Unzip the MobileCredentialVerifierSDK-*version*.xcframework.zip file.
2. Drag the MobileCredentialVerifierSDK-*version*.xcframework folder into your project.
3. Configure MobileCredentialVerifierSDK.xcframework to Embed & sign.

See Add existing files and folders for detailed instructions.

This should result in the the following framework being added to your project:

Step 3: Add Bluetooth permissions

The SDK requires access to the mobile device Bluetooth capabilities as part of the proximity presentation workflow. Configure these permissions in the Info tab of the Application target:

Step 4: Run the application

Select Run and make sure the application launches with a “Hello, world!” text in the middle of the display, as shown in the following image:

Step 1: Create a new project

1. Create a new Android Studio project, using the Empty Activity template.

2. Name the project Verifier Tutorial.
3. Select API 24 as the Minimum SDK version.
4. Select Kotlin DSL as the Build configuration language.

5. Sync the project with Gradle files.

Step 2: Add required dependencies

1. Select the Project view.

   

2. Create a new directory named repo in your project's folder.

3. Unzip the common-*version*.zip and verifier-*version*.zip files and copy the unzipped global folders into the new repo folder, merging the top-level directories.

   

4. Open the settings.gradle.kts file in the VerifierTutorial folder and add the following Maven repository to the dependencyResolutionManagement.repositories block:

   maven {
       url = uri("repo")
   }

5. Open the app/build.gradle.kts file in your app folder and add the following dependencies to the dependencies block:

implementation("global.mattr.mobilecredential:verifier:4.1.0")
implementation("androidx.navigation:navigation-compose:2.9.0")

6. Sync the project with Gradle files.

7. Open the Build tab and select Sync to make sure that the project has synced successfully.

   

Step 3: Run the application

1. Connect a debuggable mobile device to your machine.

2. Build and run the app on the connected mobile device.

   The app should launch with a “Hello, Android!” text displayed:

   

1. Open the ContentView file in your new project and replace any existing code with the following:

   import SwiftUI
   // Initialize SDK - Step 2.1: import MobileCredentialVerifierSDK
   
   struct ContentView: View {
       @ObservedObject var viewModel: VerifierViewModel = VerifierViewModel()
   
       var body: some View {
           NavigationStack(path: $viewModel.navigationPath) {
               VStack {
                   Button("Certificate Management") {
                       viewModel.navigationPath.append(NavigationState.certificateManagement)
                   }
                   .padding()
   
                   Button("Scan QR Code") {
                       viewModel.navigationPath.append(NavigationState.scanQRCode)
                   }
                   .padding()
   
                   Button("View Response") {
                       viewModel.navigationPath.append(NavigationState.viewResponse)
                   }
                   .padding()
               }
               .navigationDestination(for: NavigationState.self) { destination in
                   switch destination {
                   case .certificateManagement:
                       certificateManagementView
                   case .scanQRCode:
                       codeScannerView
                   case .viewResponse:
                       presentationResponseView
                   }
               }
           }
       }
   
       // MARK: Verification Views
   
   
       var codeScannerView: some View {
       // Verify mDocs - Step 2.4: Create QRScannerView
           EmptyView()
       }
       // Manage Certificates - Step 1.2: Create CertificateManagementView
       var certificateManagementView: some View {
           EmptyView()
       }
       var presentationResponseView: some View {
       // Verify mDocs - Step 4.2: Create PresentationResponseView
           EmptyView()
       }
   }
   
   // MARK: VerifierViewModel
   
   final class VerifierViewModel: ObservableObject {
       @Published var navigationPath = NavigationPath()
       // Initialize SDK - Step 2.2: Add MobileCredentialVerifier var
   
       // Verify mDocs - Step 1.1: Create MobileCredentialRequest instance
   
       // Verify mDocs - Step 1.2: Create receivedDocuments variable
   
       // Initialize SDK - Step 2.3: Initialize the SDK
   }
   
   // MARK: Proximity Presentation
   extension VerifierViewModel {
       func setupProximityPresentationSession(_ deviceEngagementString: String) {
       // Verify mDocs - Step 3.2: Create setupProximityPresentationSession
           print("This method will use qr code string do setup proximity session")
       }
       func sendDeviceRequest() {
       // Verify mDocs - Step 3.3: Create sendDeviceRequest function
           print("This method will send preconfigured device request to holder app")
       }
   }
   
   // Verify mDocs - Step 3.1: Extend VerifierViewModel class
   
   
   // MARK: - Navigation
   enum NavigationState: Hashable {
       case certificateManagement
       case scanQRCode
       case viewResponse
   }

Open the app/src/main/com/example/verifiertutorial/MainActivity.kt file in your project and replace any existing code with the following:

package com.example.verifiertutorial

import android.os.Bundle
import androidx.activity.ComponentActivity
import androidx.activity.compose.setContent
import androidx.activity.enableEdgeToEdge
import androidx.compose.foundation.layout.Column
import androidx.compose.foundation.layout.fillMaxSize
import androidx.compose.foundation.layout.fillMaxWidth
import androidx.compose.foundation.layout.padding
import androidx.compose.material3.Button
import androidx.compose.material3.Text
import androidx.compose.runtime.Composable
import androidx.compose.ui.Modifier
import androidx.compose.ui.unit.dp
import androidx.lifecycle.lifecycleScope
import androidx.navigation.NavController
import androidx.navigation.compose.NavHost
import androidx.navigation.compose.composable
import androidx.navigation.compose.rememberNavController
import com.example.verifiertutorial.ui.theme.VerifierTutorialTheme
import global.mattr.mobilecredential.common.dto.MobileCredentialResponse
import global.mattr.mobilecredential.verifier.MobileCredentialVerifier
import kotlinx.coroutines.launch

class MainActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        // Initialize SDK - Step 1.1: Initialize the SDK

        enableEdgeToEdge()
        setContent {
            VerifierTutorialTheme {
                val navController = rememberNavController()
                NavHost(
                    modifier = Modifier
                        .fillMaxSize()
                        .padding(vertical = 72.dp, horizontal = 8.dp),
                    startDestination = "home",
                    navController = navController,
                ) {
                    composable("home") {
                        HomeScreen(navController)
                    }
                    composable("certManagement") {
                        // Manage Certificates - Step 2.3: Add certificates management screen call
                    }
                    composable("scanOffer") {
                        // Verify mDocs - Step 1.7: Add "Scan Offer" screen call
                    }
                    composable("viewResponse") {
                        // Verify mDocs - Step 4.4: Add "View Response" screen call
                    }
                }
            }
        }
    }
}

@Composable
fun HomeScreen(navController: NavController) {
    Column(modifier = Modifier.fillMaxWidth()) {
        Button(
            modifier = Modifier.fillMaxWidth(),
            onClick = { navController.navigate("certManagement") }
        ) {
            Text("Certificate Management")
        }
        Button(
            modifier = Modifier.fillMaxWidth(),
            onClick = { navController.navigate("scanOffer") }
        ) {
            Text("Scan Presentation Offer")
        }
    }
}

// Verify mDocs - Step 2.2: Add shared data

1. Add the following code after the // Initialize SDK - Step 2.1: Import MobileCredentialVerifierSDK comment to import MobileCredentialVerifierSDK and gain access to the SDK's capabilities:

   import MobileCredentialVerifierSDK

2. Add the following code after the // Initialize SDK - Step 2.2: Add MobileCredentialVerifier var comment to create a variable that holds the mobileCredentialVerifier instance:

       var mobileCredentialVerifier: MobileCredentialVerifier

3. Add the following code after the // Initialize SDK - Step 2.3: Initialize the SDK comment to assign a shared instance of the class to our mobileCredentialVerifier variable and initialize the SDK:

       init() {
           do {
               mobileCredentialVerifier = MobileCredentialVerifier.shared
               try mobileCredentialVerifier.initialize()
           } catch {
               print(error.localizedDescription)
           }
       }

4. Run the app to ensure it compiles successfully.

Once the app launches you will see a screen with three buttons, each leading to an empty view. In the following steps, you will implement proximity presentation functionalities into these views.

1. Add the following code after the // Initialize SDK - Step 1.1: Initialize the SDK comment to initialize the SDK:

   We recommend leaving the comment text (e.g. // Initialize SDK - Step 1.1: Initialize the SDK) even after you have pasted the code snippet, as it will later help you to easily locate the step in the code.

   lifecycleScope.launch {
       MobileCredentialVerifier.initialize(this@MainActivity)
   }

2. Run the app to make sure it compiles properly.

1. Create a new file named CertificateManagementView and paste the following code in it:

   import SwiftUI
   import MobileCredentialVerifierSDK
   
   struct CertificateManagementView: View {
       @ObservedObject var viewModel = CertificateManagementViewModel()
       @State var certificateString = ""
   
       var body: some View {
           Form {
               Section(
                   header: Text("IACA Certificate").font(.headline),
                   footer: HStack {
                       Spacer()
                       Button("Add") {
                           viewModel.addCertificate(certificateString)
                       }
                       Spacer().frame(width: 30)
                       Button("Clear") {
                           certificateString = ""
                       }
                       .foregroundColor(.red)
                       .contentShape(Rectangle())
                       .frame(alignment: .trailing)
                   }
               ) {
                   TextField("IACA certificate string", text: $certificateString)
               }
   
               Section(
                   header: Text("Stored Certificates").font(.headline)
               ) {
                   certificateListView
               }
           }
           .navigationBarTitle("Certificate Setting")
           .onAppear {
               viewModel.getCertificates()
           }
       }
   
       // MARK: Certificate Management Views
       var certificateListView: some View {
       // Manage Certificates - Step 2.3: Display retrieved certificates
           EmptyView()
       }
   }
   
   final class CertificateManagementViewModel: ObservableObject {
       // Manage Certificates - Step 2.1: Add certificates and verifier variable
   
       func getCertificates() {
       // Manage Certificates - Step 2.2: Create getCertificates function
           print("This will fetch certificates from storage")
       }
   
       func addCertificate(_ certificate: String) {
       // Manage Certificates - Step 2.4: Create addCertificate function
           print("This will add certificate to storage and get a new list of certificates")
       }
       func removeCertificate(_ certificateID: String) {
       // Manage Certificates - Step 2.5: Create removeCertificate function
           print("This will remove certificates from storage and get a new list of certificates")
       }
   }

The CertificateManagementView file provides a basic user interface for displaying a list of certificates and controls for managing certificate storage. The CertificateManagementViewModel class contains the logic for adding, retrieving, and removing certificates.

2. Return to the ContentView file and replace the EmptyView() under the // Manage certificates - Step 1.2: Create CertificateManagementView comment with a reference to the new view you created in the previous step:

       CertificateManagementView()

3. Run the app and select the Certificate Management button. You should see a result similar to the following:

As the user selects the Certificate Management button they are navigated to the new CertificateManagement view where they can see controls that would enable them to add, view and remove certificates. We will build these capabilities into the controls in the next step.

1. In your package, create a new file CertManagementScreen.kt.

   

2. Add the following code to the file to display the basic UI that enables the user to add, view and remove certificates:

   import androidx.compose.foundation.layout.Arrangement
   import androidx.compose.foundation.layout.Column
   import androidx.compose.foundation.layout.Row
   import androidx.compose.foundation.layout.fillMaxSize
   import androidx.compose.foundation.layout.fillMaxWidth
   import androidx.compose.foundation.layout.height
   import androidx.compose.foundation.layout.padding
   import androidx.compose.foundation.lazy.LazyColumn
   import androidx.compose.foundation.lazy.items
   import androidx.compose.material.icons.Icons
   import androidx.compose.material.icons.filled.Delete
   import androidx.compose.material3.Card
   import androidx.compose.material3.Icon
   import androidx.compose.material3.IconButton
   import androidx.compose.material3.MaterialTheme
   import androidx.compose.material3.Text
   import androidx.compose.material3.TextButton
   import androidx.compose.material3.TextField
   import androidx.compose.runtime.Composable
   import androidx.compose.runtime.LaunchedEffect
   import androidx.compose.runtime.getValue
   import androidx.compose.runtime.mutableStateOf
   import androidx.compose.runtime.remember
   import androidx.compose.runtime.setValue
   import androidx.compose.ui.Alignment
   import androidx.compose.ui.Modifier
   import androidx.compose.ui.unit.dp
   import global.mattr.mobilecredential.common.dto.TrustedCertificate
   import global.mattr.mobilecredential.verifier.MobileCredentialVerifier
   
   @Composable
   fun CertManagementScreen() {
       Column(modifier = Modifier.fillMaxSize(), verticalArrangement = Arrangement.spacedBy(4.dp)) {
           var certText by remember { mutableStateOf("") }
           var storedCerts by remember { mutableStateOf(listOf<TrustedCertificate>()) }
           // Manage Certificates - Step 2.3: Load certificates when screen enters the composition
   
           Text("IACA CERT", style = MaterialTheme.typography.titleMedium)
           TextField(
               modifier = Modifier.fillMaxWidth(),
               value = certText,
               onValueChange = { certText = it },
               singleLine = true
           )
           Row(modifier = Modifier.fillMaxWidth(), horizontalArrangement = Arrangement.End) {
               // Manage Certificates - Step 2.1: Add "Add certificate" button
   
               TextButton(onClick = { certText = "" }) { Text("Clear") }
           }
   
           Text("STORED CERTIFICATES", style = MaterialTheme.typography.titleMedium)
           LazyColumn(
               modifier = Modifier.fillMaxWidth(),
               verticalArrangement = Arrangement.spacedBy(6.dp)
           ) {
               items(storedCerts, key = { it.id }) { cert ->
                   Row(modifier = Modifier.fillMaxWidth()) {
                       Card(Modifier.weight(1f).height(85.dp)) {
                           Text(cert.pem, Modifier.padding(6.dp))
                       }
   
                       // Manage Certificates - Step 2.2: Add "Delete certificate" button
                   }
               }
           }
       }
   }

3. Back in the MainActivity file, add the following code under the // Manage Certificates - Step 2.3: Add certificates management screen call comment to connect the created composable to the navigation graph:

   CertManagementScreen()

4. Run the app and select the Certificate Management button. You should be navigated to the new certificate management screen, where you can see controls that would enable the user to add, view and remove certificates. We will build these capabilities into the controls in the next step.

1. Open the CertificateManagementView file and add the following code under the // Manage Certificates - Step 2.1: Add certificates variable comment to add a new certificates variable that will hold the certificates added to the application and a reference to a shared instance of MobileCredentialVerifier:

       @Published var certificates: [TrustedCertificate] = []
       let mobileCredentialVerifier = MobileCredentialVerifier.shared

2. Replace the print statement under the // Manage Certificates - Step 2.2: Create getCertificates function comment to call the SDK getTrustedIssuerCertificates, retrieve all certificates and display them to the user:

           do {
               let fetchedCertificates = try mobileCredentialVerifier.getTrustedIssuerCertificates()
               certificates = fetchedCertificates
           } catch {
               print(error.localizedDescription)
           }

3. Replace the EmptyView() under the // Manage Certificates - Step 2.3: Display retrieved certificates comment to iterate over retrieved certificates and display them to the user:

       ForEach(viewModel.certificates, id: \.id) { certificate in
           Text("\(certificate.pem)")
               .frame(maxHeight: 100)
               .swipeActions(edge: .trailing) {
                   Button(role:. destructive) {
                       viewModel.removeCertificate(certificate.id)
                   } label: {
                       Image(systemName: "trash")
                   }
               }
       }

4. Replace the print statement under the // Manage Certificates - Step 2.4: Create addCertificate function comment to call the SDK addTrustedIssuerCertificates, accept a string parameter and use it to add a new certificate:

       Task { @MainActor in
           do {
               _ = try await mobileCredentialVerifier.addTrustedIssuerCertificates(certificates: [certificate])
               self.getCertificates()
           }
           catch {
               print(error.localizedDescription)
           }
       }

5. Replace the print statement under the // Manage Certificates - Step 2.5: Create removeCertificate function to call the SDK deleteTrustedIssuerCertificate and remove a selected certificate:

       do {
           try mobileCredentialVerifier.deleteTrustedIssuerCertificate(certificateId: certificateID)
           // Refresh the certificates list after deletion
           self.getCertificates()
       } catch {
           print(error.localizedDescription)
       }

6. Run the app and perform the following instructions:

   1. Select the Manage Certificates button.

   2. Copy and paste the following text into the IACA Certificate text box.

      MIICYzCCAgmgAwIBAgIKXhjLoCkLWBxREDAKBggqhkjOPQQDAjA4MQswCQYDVQQG
      EwJBVTEpMCcGA1UEAwwgbW9udGNsaWZmLWRtdi5tYXR0cmxhYnMuY29tIElBQ0Ew
      HhcNMjQwMTE4MjMxNDE4WhcNMzQwMTE1MjMxNDE4WjA4MQswCQYDVQQGEwJBVTEp
      MCcGA1UEAwwgbW9udGNsaWZmLWRtdi5tYXR0cmxhYnMuY29tIElBQ0EwWTATBgcq
      hkjOPQIBBggqhkjOPQMBBwNCAASBnqobOh8baMW7mpSZaQMawj6wgM5e5nPd6HXp
      dB8eUVPlCMKribQ7XiiLU96rib/yQLH2k1CUeZmEjxoEi42xo4H6MIH3MBIGA1Ud
      EwEB/wQIMAYBAf8CAQAwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRFZwEOI9yq
      232NG+OzNQzFKa/LxDAuBgNVHRIEJzAlhiNodHRwczovL21vbnRjbGlmZi1kbXYu
      bWF0dHJsYWJzLmNvbTCBgQYDVR0fBHoweDB2oHSgcoZwaHR0cHM6Ly9tb250Y2xp
      ZmYtZG12LnZpaS5hdTAxLm1hdHRyLmdsb2JhbC92Mi9jcmVkZW50aWFscy9tb2Jp
      bGUvaWFjYXMvMjk0YmExYmMtOTFhMS00MjJmLThhMTctY2IwODU0NWY0ODYwL2Ny
      bDAKBggqhkjOPQQDAgNIADBFAiAlZYQP95lGzVJfCykhcpCzpQ2LWE/AbjTGkcGI
      SNsu7gIhAJfP54a2hXz4YiQN4qJERlORjyL1Ru9M0/dtQppohFm6

3. Select the Add button. The new certificate should appear in the STORED CERTIFICATES area.

4. Swipe left across the new certificate and select the Delete icon to remove it.

You should get a result similar to the following:

1. When the user selects the Certificate Management button they are navigated to the CertificateManagement view.
2. When the user adds the text and selects the Add button a new certificate is added and displayed in the STORED CERTIFICATES area.
3. When the user swipes left and selects the Delete icon the certificate is removed.

You have now built the capabilities required to manage certificates into your applications. Now we can proceed to building the capabilities to handle the actual presentation workflow.

1. Open the CertManagementScreen.kt file and add the following code under the // Manage Certificates - Step 2.1: Add "Add certificate" button comment to add a button, that will be responsible for adding the certificate, entered in the text field above:

   TextButton(
       onClick = {
           MobileCredentialVerifier.addTrustedIssuerCertificates(listOf(certText))
           storedCerts = MobileCredentialVerifier.getTrustedIssuerCertificates()
       }
   ) { Text("Add") }

2. Add the following code under the // Manage Certificates - Step 2.2: Add "Delete certificate" button comment to add a button, that will delete the certificate, when pressed:

   IconButton(
       onClick = {
           MobileCredentialVerifier.deleteTrustedIssuerCertificate(cert.id)
           storedCerts = MobileCredentialVerifier.getTrustedIssuerCertificates()
       },
       modifier = Modifier.align(Alignment.CenterVertically)
   ) {
       Icon(
           Icons.Default.Delete,
           contentDescription = "Delete Cert",
           tint = MaterialTheme.colorScheme.primary
       )
   }

3. Add the following code under the // Manage Certificates - Step 2.3: Load certificates when screen enters the composition comment to enable loading the certificates from the local storage and showing them, when the screen enters the composition:

   LaunchedEffect(Unit) {
       storedCerts = MobileCredentialVerifier.getTrustedIssuerCertificates()
   }

4. Run the app and perform the following instructions:

   1. Select the Manage Certificates button.

   2. Copy and paste the following text into the IACA Certificate text box.

      MIICYzCCAgmgAwIBAgIKXhjLoCkLWBxREDAKBggqhkjOPQQDAjA4MQswCQYDVQQG
      EwJBVTEpMCcGA1UEAwwgbW9udGNsaWZmLWRtdi5tYXR0cmxhYnMuY29tIElBQ0Ew
      HhcNMjQwMTE4MjMxNDE4WhcNMzQwMTE1MjMxNDE4WjA4MQswCQYDVQQGEwJBVTEp
      MCcGA1UEAwwgbW9udGNsaWZmLWRtdi5tYXR0cmxhYnMuY29tIElBQ0EwWTATBgcq
      hkjOPQIBBggqhkjOPQMBBwNCAASBnqobOh8baMW7mpSZaQMawj6wgM5e5nPd6HXp
      dB8eUVPlCMKribQ7XiiLU96rib/yQLH2k1CUeZmEjxoEi42xo4H6MIH3MBIGA1Ud
      EwEB/wQIMAYBAf8CAQAwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRFZwEOI9yq
      232NG+OzNQzFKa/LxDAuBgNVHRIEJzAlhiNodHRwczovL21vbnRjbGlmZi1kbXYu
      bWF0dHJsYWJzLmNvbTCBgQYDVR0fBHoweDB2oHSgcoZwaHR0cHM6Ly9tb250Y2xp
      ZmYtZG12LnZpaS5hdTAxLm1hdHRyLmdsb2JhbC92Mi9jcmVkZW50aWFscy9tb2Jp
      bGUvaWFjYXMvMjk0YmExYmMtOTFhMS00MjJmLThhMTctY2IwODU0NWY0ODYwL2Ny
      bDAKBggqhkjOPQQDAgNIADBFAiAlZYQP95lGzVJfCykhcpCzpQ2LWE/AbjTGkcGI
      SNsu7gIhAJfP54a2hXz4YiQN4qJERlORjyL1Ru9M0/dtQppohFm6

3. Select the Add button. The new certificate should appear in the STORED CERTIFICATES area.

4. Press Delete icon to remove the certificate.

You should get a result similar to the following:

1. When the user selects the Certificate Management button they are navigated to the CertManagementScreen.
2. When the user adds the text and selects the Add button a new certificate is added and displayed in the STORED CERTIFICATES area.
3. When the user selects the Delete icon the certificate is removed.

Step 1: Create a presentation request

As a verifier, you can select what information you request for verification. Your application implements this by creating a MobileCredentialRequest instance to define the required information, and a new variable to hold the response from the wallet application.

1. Open the ContentView file and add the following code under the // Verify mDocs - Step 1.1: Create MobileCredentialRequest instance comment to define what information to request from the wallet application user:

       let mobileCredentialRequest = MobileCredentialRequest(
           docType: "org.iso.18013.5.1.mDL",
           namespaces: [
               "org.iso.18013.5.1":  [
                   "family_name": false,
                   "given_name": false,
                   "birth_date": false
               ]
           ]
       )

   This object details:

   • The requested credential type (e.g. org.iso.18013.5.1.mDL).
   • The claims required for verification (e.g. family_name).
   • The requested namespace (e.g. org.iso.18013.5.1).
   • Whether or not the verifier intends to persist the claim value (true/false).

   For the verification to be successful, the presented credential must include the referenced claim against the specific namespace defined in the request. Our example requests the birth_date under the org.iso.18013.5.1 namespace. If a wallet responds to this request with a credential that includes a birth_date but rather under the org.iso.18013.5.1.US namespace, the claim will not be verified.

2. Add the following code under the Verify mDocs - Step 1.2: Create receivedDocuments variable comment to create a new receivedDocuments variable that will hold the response from the wallet application:

       @Published var receivedDocuments: [MobileCredentialPresentation] = []

Your application now has an existing credential request to share, and a variable to hold any incoming responses. In the next step we will build the capabilities to send this request and handle the response.

Step 2: Scan and process a QR code

As defined in ISO/IEC 18130-5:2021, a proximity presentation workflow is always initiated by the holder (wallet application user), who must create a QR code for the verifier to scan in order to initiate the device engagement phase.

This means that your verifier application must be able to scan and process this QR code. For ease of implementation, we will use a third party framework to achieve this.

1. Add camera usage permissions to the app target:

2. Add the CodeScanner library via Swift Package Manager.

3. Create a new swift file named QRScannerView and add the following code into it to implement the QR scanning capability:

   import SwiftUI
   import CodeScanner
   
   struct QRScannerView: View {
   
       private let completionHandler: (String) -> Void
   
       init(completion: @escaping (String) -> Void) {
           completionHandler = completion
       }
   
       var body: some View {
           CodeScannerView(codeTypes: [.qr]) { result in
               switch result {
               case .failure(let error):
                   print(error.localizedDescription)
               case .success(let result):
                   print(result.string)
                   completionHandler(result.string)
               }
           }
       }
   }

4. Back in the ContentView file, replace the EmptyView() under the // Verify mDocs - Step 2.4: Create QRScannerView comment with the following code to create a new app view that the user will use to scan a QR code:

       QRScannerView(
           completion: { string in
               viewModel.setupProximityPresentationSession(string)
           }
       )

5. Run the app and select the Scan QR Code button. You should be navigated to the new QRScannerView where you can use the camera to scan a QR code.

Next we will build the logic that handles this QR code to establish a secure connection with the wallet application.

Step 1: Create a screen for scanning the credential offer

As defined in ISO/IEC 18130-5:2021, a proximity presentation workflow is always initiated by the holder (wallet application user), who must create a QR code for the verifier to scan in order to initiate the device engagement phase.

This means that your verifier application must be able to scan and process this QR code. For ease of implementation, we will use a third party framework to achieve this.

1. Add dependencies to your app/build.gradle.kts:

   implementation("com.google.accompanist:accompanist-permissions:0.36.0")
   implementation("com.journeyapps:zxing-android-embedded:4.3.0")

2. Sync project with Gradle files.

3. In your package, create a new file called ScanOfferScreen.kt and add the following code:

   import android.app.Activity
   import android.Manifest
   import android.widget.Toast
   import androidx.activity.compose.rememberLauncherForActivityResult
   import androidx.activity.result.contract.ActivityResultContracts
   import androidx.compose.foundation.layout.Box
   import androidx.compose.foundation.layout.fillMaxSize
   import androidx.compose.material3.CircularProgressIndicator
   import androidx.compose.runtime.Composable
   import androidx.compose.runtime.DisposableEffect
   import androidx.compose.runtime.LaunchedEffect
   import androidx.compose.runtime.getValue
   import androidx.compose.runtime.mutableStateOf
   import androidx.compose.runtime.remember
   import androidx.compose.runtime.rememberCoroutineScope
   import androidx.compose.runtime.setValue
   import androidx.compose.ui.Alignment
   import androidx.compose.ui.Modifier
   import androidx.compose.ui.platform.LocalContext
   import androidx.compose.ui.viewinterop.AndroidView
   import androidx.navigation.NavController
   import com.google.accompanist.permissions.ExperimentalPermissionsApi
   import com.google.accompanist.permissions.isGranted
   import com.google.accompanist.permissions.rememberPermissionState
   import com.journeyapps.barcodescanner.BarcodeCallback
   import com.journeyapps.barcodescanner.DecoratedBarcodeView
   import global.mattr.mobilecredential.common.deviceretrieval.devicerequest.DataElements
   import global.mattr.mobilecredential.common.deviceretrieval.devicerequest.NameSpaces
   import global.mattr.mobilecredential.common.dto.MobileCredentialRequest
   import global.mattr.mobilecredential.common.dto.MobileCredentialResponse
   import global.mattr.mobilecredential.verifier.MobileCredentialVerifier
   import global.mattr.mobilecredential.verifier.ProximityPresentationSessionListener
   import kotlinx.coroutines.CoroutineScope
   import kotlinx.coroutines.launch
   import kotlinx.coroutines.suspendCancellableCoroutine
   import kotlin.coroutines.Continuation
   import kotlin.coroutines.resume
   import kotlin.coroutines.resumeWithException
   
   @OptIn(ExperimentalPermissionsApi::class)
   @Composable
   fun ScanOfferScreen(activity: Activity, navController: NavController) {
       // Verify mDocs - Step 1.6: Add permission request logic
   }
   
   // Verify mDocs - Step 1.5: Add screen content
   
   // Verify mDocs - Step 1.4: Add QR scan callback
   
   // Verify mDocs - Step 3.1: Create session listener
   
   // Verify mDocs - Step 2.1: Create a sample request

4. In the ScanOfferScreen.kt file, add the following code under the // Verify mDocs - Step 1.4: Add QR scan callback comment to define a callback that is called when the QR code was successfully scanned (we will implement the callback logic at a later stage):

    private fun onQrScanned(
        activity: Activity,
        deviceEngagement: String,
        coroutineScope: CoroutineScope,
        navController: NavController
    ) {
        coroutineScope.launch {
            // Verify mDocs - Step 3.2: Create session
   
            // Verify mDocs - Step 4.1: Handle response
        }
    }

5. Add the following code under the // Verify mDocs - Step 1.5: Add screen content comment to define the main UI of the screen:

    @Composable
    private fun Content(activity: Activity, navController: NavController) {
        val context = LocalContext.current
        val barcodeView = remember { DecoratedBarcodeView(context) }
        val coroutineScope = rememberCoroutineScope()
        var isQrScanned by remember { mutableStateOf(false) }
   
        val barcodeCallback = remember {
            BarcodeCallback { result ->
                onQrScanned(activity, result.text, coroutineScope, navController)
                barcodeView.pause()
                isQrScanned = true
            }
        }
   
        DisposableEffect(Unit) {
            barcodeView.decodeContinuous(barcodeCallback)
            barcodeView.resume()
            onDispose { barcodeView.pause() }
        }
   
        if (!isQrScanned) {
            AndroidView(factory = { barcodeView }, modifier = Modifier.fillMaxSize())
        } else {
            Box(Modifier.fillMaxSize()) {
                CircularProgressIndicator(Modifier.align(Alignment.Center))
            }
        }
    }

   Please have a quick look at the code. The screen will show a QR scanning view. As soon as the QR code is captured, it shows a progress spinning wheel, and calls onQrScanned function.

6. Add the following code under the // Verify mDocs - Step 1.6: Add permission request logic comment to define a basic logic for requesting the camera access permission at runtime:

   val cameraPermissionState = rememberPermissionState(Manifest.permission.CAMERA)
   
   val requestPermissionLauncher =
       rememberLauncherForActivityResult(ActivityResultContracts.RequestPermission()) {}
   
   LaunchedEffect(cameraPermissionState) {
       if (!cameraPermissionState.status.isGranted) {
           requestPermissionLauncher.launch(Manifest.permission.CAMERA)
       }
   }
   
   if (cameraPermissionState.status.isGranted) Content(activity, navController)

7. Back in the MainActivity file, add the following code under the // Verify mDocs - Step 1.7: Add "Scan Offer" screen call to connect the created screen to the navigation graph:

   ScanOfferScreen(this@MainActivity, navController)

8. Run the app and select the Scan QR Code button. You should be navigated to the new QRScannerView where you can use the camera to scan a QR code.

Now we will build the logic that handles this QR code to establish a secure connection with the wallet application.

Step 2: Create a presentation request

As a verifier, you can select what information you request for verification. Our application implements this by creating a MobileCredentialRequest instance to define the required information, and a new variable to hold the response from the wallet application.

1. In the ScanOfferScreen.kt file, add the following code under the // Verify mDocs - Step 2.1: Create a sample request comment to define what information to request from the holder's application:

    private val sampleMdocRequest = MobileCredentialRequest(
        docType = "org.iso.18013.5.1.mDL",
        namespaces = NameSpaces(
            mapOf(
                "org.iso.18013.5.1" to DataElements(
                    listOf("given_name", "family_name", "birth_date").associateWith { false }
                )
            )
        )
    )

   This object details:

   • The requested credential type (e.g. org.iso.18013.5.1.mDL).
   • The claims required for verification (e.g. given_name).
   • The requested namespace (e.g. org.iso.18013.5.1).
   • Whether or not the verifier intends to persist the claim value (true/false).

   For the verification to be successful, the presented credential must include the referenced claim against the specific namespace defined in the request. Our example requests the birth_date under the org.iso.18013.5.1 namespace. If a wallet responds to this request with a credential that includes a birth_date but rather under the org.iso.18013.5.1.US namespace, the claim will not be verified.

2. Back in the MainActivity.kt file, add the following code under the // Verify mDocs - Step 2.2: Add shared data comment to create a new credentialResponse variable that will hold the response from the holder's application:

    object SharedData {
   
        var credentialResponse: MobileCredentialResponse? = null
    }

Now your application has an existing request to share, and a variable to hold any incoming responses. We can now proceed to build the capabilities to send the request and handle the response.

1. Add the following code under the Verify mDocs - Step 3.1: Extend VerifierViewModel class to extend the VerifierViewModel class with the ProximityPresentationSessionListener protocol:

   extension VerifierViewModel: ProximityPresentationSessionListener {
   
               public func onEstablished() {
                   sendDeviceRequest()
               }
   
               public func onTerminated(error: (any Error)?) {
                   print("Session Terminated")
               }
           }

   Now, as soon as a connection is established, the app will send a device request. You will implement the functionality of sendDeviceRequest() in VerifierViewModel later in the tutorial.

2. Replace the print statement under the // Verify mDocs - Step 3.2: Create setupProximityPresentationSession comment with the following code to call the SDK's createProximityPresentationSession function, passing a device engagement string (retrieved from a QR code) and self as a listener to create a proximity presentation session:

    mobileCredentialVerifier.createProximityPresentationSession(encodedDeviceEngagementString: deviceEngagementString, listener: self)

3. Replace the print statement under the // Verify mDocs - Step 3.3: Create sendDeviceRequest function comment with following code to implement the logic to send a device request:

       Task { @MainActor in
           receivedDocuments = []
           do {
               // Navigate to response screen
               navigationPath.append(NavigationState.viewResponse)
               // Request mDocs
               let deviceResponse = try await mobileCredentialVerifier.sendProximityPresentationRequest(
                   request: [mobileCredentialRequest]
               )
   
               // Assign new values from the response
               receivedDocuments = deviceResponse.credentials ?? []
               // Terminate session after response is received (optional)
               await mobileCredentialVerifier.terminateProximityPresentationSession()
           } catch {
               print(error)
               receivedDocuments = []
           }
       }

   This function now implements the following logic:

   1. Navigate to the viewResponse screen.
   2. Send a proximity presentation request using the SDK's requestMobileCredentials function.
   3. Store the wallet response in the deviceResponse variable. This includes the verification results of any credentials included in the response.
   4. Store the verification results in the receivedDocuments variable.
   5. Terminate the presentation session once the response is received.

1. In ScanOfferScreen.kt, add the following code under the // Verify mDocs - Step 3.1: Create session listener to define a listener that will react to the proximity presentation session lifecycle events:

   private class SessionListener(
       private val coroutineScope: CoroutineScope,
       private val continuation: Continuation<MobileCredentialResponse>
   ) : ProximityPresentationSessionListener {
       override fun onEstablished() {
           coroutineScope.launch {
               // Verify mDocs - Step 3.3: Request credentials
           }
       }
   
       override fun onTerminated(error: Throwable?) {
           /* no-op */
       }
   
       override fun onError(error: Throwable?) {
           error?.let { continuation.resumeWithException(it) }
       }
   }

2. Add the following code under the // Verify mDocs - Step 3.2: Create session to create proximity presentation session and register a session listener:

   SharedData.credentialResponse = try {
       suspendCancellableCoroutine { continuation: Continuation<MobileCredentialResponse> ->
           val sessionListener = SessionListener(coroutineScope, continuation)
   
           MobileCredentialVerifier
               .createProximityPresentationSession(activity, deviceEngagement, sessionListener)
       }
   } catch (e: Exception) {
       Toast.makeText(activity, "Failed to request credentials", Toast.LENGTH_SHORT).show()
       null
   }

   We pass Continuation to the listener. It will be resumed either with MobileCredentialResponse if the whole presentation flow is successful, or with an exception if there was an issue during any stage of the credentials presentation.

3. Add the following code under the // Verify mDocs - Step 3.3: Request credentials to request the mobile credentials:

    try {
        val response = MobileCredentialVerifier.sendProximityPresentationRequest(
            listOf(sampleMdocRequest),
            skipStatusCheck = true
        )
        MobileCredentialVerifier.terminateProximityPresentationSession()
        continuation.resume(response)
    } catch (e: Exception) {
        continuation.resumeWithException(e)
    }

The resulting code:

1. Establishes a secure connection with the wallet application by calling createProximityPresentationSession.
2. Calls sendProximityPresentationRequest function as soon as the session is established. The function accepts a list of MobileCredentialRequests , sends the requests to the wallet application, receives a response from the wallet application, and verifies any mDocs included in the response.
3. Stores the response in the SharedData.credentialResponse value.
4. Handles the exceptions, if they were thrown from the above calls. An exception can be thrown if, for example, the Bluetooth connection between the Holder and Verifier devices was interrupted during the session.

Now that we have the verification results stored, you can implement different business logics to handle the results.

For this tutorial, we will display these results to the verifier app user, individually indicating the verification status of each claim included in the request.

1. Create a new file named DocumentView and add the following code to display available verification results:

   import MobileCredentialVerifierSDK
   import SwiftUI
   
       struct DocumentView: View {
   
           var viewModel: DocumentViewModel
   
           var body: some View {
               VStack(alignment: .leading, spacing: 10) {
                   Text(viewModel.docType)
                       .font(.title)
                       .fontWeight(.bold)
                       .padding(.bottom, 5)
   
                   Text(viewModel.verificationResult)
                       .font(.title)
                       .fontWeight(.bold)
                       .foregroundStyle(viewModel.verificationFailedReason == nil ? .green : .red)
                       .padding(.bottom, 5)
   
                   if let verificationFailedReason = viewModel.verificationFailedReason {
                       Text(verificationFailedReason)
                           .font(.title3)
                           .fontWeight(.bold)
                           .foregroundStyle(.red)
                           .padding(.bottom, 5)
                   }
   
                   ForEach(viewModel.namespacesAndClaims.keys.sorted(), id: \.self) { key in
                       VStack(alignment: .leading, spacing: 5) {
                           Text(key)
                               .font(.headline)
                               .padding(.vertical, 5)
                               .padding(.horizontal, 10)
                               .background(Color.gray.opacity(0.2))
                               .cornerRadius(5)
   
                           ForEach(viewModel.namespacesAndClaims[key]!.keys.sorted(), id: \.self) { claim in
                               HStack {
                                   Text(claim)
                                       .fontWeight(.semibold)
                                   Spacer()
                                   Text(viewModel.namespacesAndClaims[key]![claim]! ?? "")
                                       .fontWeight(.regular)
                               }
                               .padding(.vertical, 5)
                               .padding(.horizontal, 10)
                               .background(Color.white)
                               .cornerRadius(5)
                               .shadow(radius: 1)
                           }
                       }
                       .padding(.vertical, 5)
                   }
   
                   if !viewModel.claimErrors.isEmpty {
                   Text("Failed Claims:")
                       .font(.headline)
                       .padding(.vertical, 5)
   
                       ForEach(viewModel.claimErrors.keys.sorted(), id: \.self) { key in
                           VStack(alignment: .leading, spacing: 5) {
                               Text(key)
                                   .font(.headline)
                                   .padding(.vertical, 5)
                                   .padding(.horizontal, 10)
                                   .background(Color.gray.opacity(0.2))
                                   .cornerRadius(5)
   
                               ForEach(viewModel.claimErrors[key]!.keys.sorted(), id: \.self) { claim in
                                   HStack {
                                       Text(claim)
                                           .fontWeight(.semibold)
                                       Spacer()
                                       Text(viewModel.claimErrors[key]![claim]! ?? "")
                                           .fontWeight(.regular)
                                   }
                                   .padding(.vertical, 5)
                                   .padding(.horizontal, 10)
                                   .background(Color.white)
                                   .cornerRadius(5)
                                   .shadow(radius: 1)
                               }
                           }
                           .padding(.vertical, 5)
                       }
                   }
               }
               .padding()
               .background(RoundedRectangle(cornerRadius: 10).fill(Color.white).shadow(radius: 5))
               .padding(.horizontal)
           }
       }
   
       // MARK: DocumentViewModel
   
       class DocumentViewModel: ObservableObject {
           let docType: String
           let namespacesAndClaims: [String: [String: String?]]
           let claimErrors: [String: [String: String?]]
           let verificationResult: String
           let verificationFailedReason: String?
   
           init(from presentation: MobileCredentialPresentation) {
               self.docType = presentation.docType
               self.verificationResult = presentation.verificationResult.verified ? "Verified" : "Invalid"
               self.verificationFailedReason = presentation.verificationResult.reason?.message
   
               self.namespacesAndClaims = presentation.claims?.reduce(into: [String: [String: String]]()) { result, outerElement in
                   let (outerKey, innerDict) = outerElement
                   result[outerKey] = innerDict.mapValues { $0.textRepresentation }
               } ?? [:]
   
               self.claimErrors = presentation.claimErrors?.reduce(into: [String: [String: String]]()) { result, outerElement in
                   let (outerKey, innerDict) = outerElement
                   result[outerKey] = innerDict.mapValues { "\($0)" }
               } ?? [:]
           }
       }
   
       // MARK: Helper
       extension MobileCredentialElementValue {
           var textRepresentation: String {
               switch self {
               case .bool(let bool):
                   return "\(bool)"
               case .string(let string):
                   return string
               case .int(let int):
                   return "\(int)"
               case .unsigned(let uInt):
                   return "\(uInt)"
               case .float(let float):
                   return "\(float)"
               case .double(let double):
                   return "\(double)"
               case let .date(date):
                   let dateFormatter = DateFormatter()
                   dateFormatter.dateStyle = .short
                   dateFormatter.timeStyle = .none
                   return dateFormatter.string(from: date)
               case let .dateTime(date):
                   let dateFormatter = DateFormatter()
                   dateFormatter.dateStyle = .short
                   dateFormatter.timeStyle = .short
                   return dateFormatter.string(from: date)
               case .data(let data):
                   return "Data \(data.count) bytes"
               case .map(let dictionary):
                   let result = dictionary.mapValues { value in
                       value.textRepresentation
                   }
                   return "\(result)"
               case .array(let array):
                   return array.reduce("") { partialResult, element in
                       partialResult + element.textRepresentation
                   }
                   .appending("")
               @unknown default:
                   return "Unknown type"
               }
           }
       }

   The DocumentView file comprises the following elements:

   • DocumentView : Basic UI layout for viewing received documents and verification results.
   • DocumentViewModel : This class takes MobileCredentialPresentation and converts its elements into strings to display in the DocumentView.
   • Extension of MobileCredentialElementValue which converts the values of received claims into a human-readable format.

2. Return to the ContentView file and replace the EmptyView() under the // Verify mDocs - Step 4.2: Create PresentationResponseView comment with the following code to display the DocumentView view when verification results are available:

           ZStack {
           if viewModel.receivedDocuments.isEmpty {
               VStack(spacing: 40) {
                   Text("Waiting for response...")
                       .font(.title)
                   ProgressView()
                       .progressViewStyle(.circular)
                       .scaleEffect(2)
               }
           } else {
               ScrollView {
                   ForEach(viewModel.receivedDocuments, id: \.docType) { doc in
                       DocumentView(viewModel: DocumentViewModel(from: doc))
                           .padding(10)
                   }
               }
           }
       }

1. Add the following code under the // Verify mDocs - Step 4.1: Handle response to navigate the user to the response screen, where they can see the retrieved credentials, if the retrieval was successful:

   SharedData.credentialResponse?.let {
      navController.navigate("viewResponse") { popUpTo("home") }
   }

2. Create a new file named ViewResponseScreen.kt that will be used to display the response to the verifier application user.

3. Copy and paste the following code into the new file:

   import androidx.compose.foundation.layout.Arrangement
   import androidx.compose.foundation.layout.Box
   import androidx.compose.foundation.layout.Column
   import androidx.compose.foundation.layout.ColumnScope
   import androidx.compose.foundation.layout.Row
   import androidx.compose.foundation.layout.Spacer
   import androidx.compose.foundation.layout.fillMaxSize
   import androidx.compose.foundation.layout.fillMaxWidth
   import androidx.compose.foundation.layout.padding
   import androidx.compose.foundation.rememberScrollState
   import androidx.compose.foundation.verticalScroll
   import androidx.compose.material3.Card
   import androidx.compose.material3.MaterialTheme
   import androidx.compose.material3.Text
   import androidx.compose.runtime.Composable
   import androidx.compose.ui.Alignment
   import androidx.compose.ui.Modifier
   import androidx.compose.ui.graphics.Color
   import androidx.compose.ui.text.style.TextOverflow
   import androidx.compose.ui.unit.dp
   import global.mattr.mobilecredential.common.deviceretrieval.deviceresponse.DataElementIdentifier
   import global.mattr.mobilecredential.common.deviceretrieval.deviceresponse.NameSpace
   import global.mattr.mobilecredential.common.dto.MobileCredentialElement
   
   @Composable
   fun ViewResponseScreen() {
       // Verify mDocs - Step 4.5: Define content
   }
   
   // Verify mDocs - Step 4.8: Display claims
   
   // Verify mDocs - Step 4.7: Map a claim or an error to string

4. Back in the MainActivity.kt file, add the following code under the // Verify mDocs - Step 4.4: Add "View Response" screen call comment to connect the created composable to the navigation graph:

   ViewResponseScreen()

5. Return to the ViewResponseScreen.kt screen and add the following code under the // Verify mDocs - Step 4.5: Define content comment to define the basic UI for displaying the response details to the verifier application user:

   val credential = SharedData.credentialResponse?.credentials?.firstOrNull()
   if (credential == null || SharedData.credentialResponse?.credentialErrors != null) {
       // Verify mDocs - Step 4.6: Show error
   } else {
       Column(
           modifier = Modifier
               .fillMaxSize()
               .verticalScroll(rememberScrollState()),
           verticalArrangement = Arrangement.spacedBy(4.dp),
       ) {
           // Verify mDocs - Step 4.10: Show credential verification status
   
           // Verify mDocs - Step 4.9: Show retrieved claims and errors
       }
   }

6. Add the following code under the // Verify mDocs - Step 4.6: Show error comment to show an error message in case the response is empty or if there were major errors during the response retrieval:

   Box(Modifier.fillMaxSize()) {
       Text("There were errors while receiving the response", Modifier.align(Alignment.Center))
   }

7. Add the following code under the // Verify mDocs - Step 4.7: Map a claim or an error to string comment to map the received claim value (or a claim error) to a string:

   private fun Any.claimToUiString() = when (this) {
       is MobileCredentialElement -> {
           when (this) {
               is MobileCredentialElement.ArrayElement, is MobileCredentialElement.DataElement,
               is MobileCredentialElement.MapElement -> this::class.simpleName ?: "Unknown element"
   
               else -> value.toString()
           }
       }
   
       else -> "Not returned"
   }

8. Add the following code under the // Verify mDocs - Step 4.8: Display claims comment to create a function that displays the retrieved and failed claims to the verifier application user:

   @Composable
   private fun ColumnScope.Claims(
       title: String,
       claims: Map<NameSpace, Map<DataElementIdentifier, Any>>?
   ) {
       Text(
           title,
           modifier = Modifier
               .fillMaxWidth()
               .align(Alignment.CenterHorizontally),
           style = MaterialTheme.typography.titleLarge
       )
       claims?.forEach { (namespace, claims) ->
           Card {
               Column(Modifier.padding(6.dp)) {
                   Text(
                       namespace,
                       style = MaterialTheme.typography.titleMedium,
                       modifier = Modifier.padding(vertical = 4.dp)
                   )
                   claims.forEach { (name, value) ->
                       Row {
                           Text(name,
                               Modifier
                                   .weight(1f)
                                   .padding(end = 4.dp))
                           Text(value.claimToUiString(), overflow = TextOverflow.Ellipsis)
                       }
                   }
               }
           }
       } ?: Text("Nothing here")
   }

9. Add the following code under the // Verify mDocs - Step 4.9: Show retrieved claims and errors comment to create the UI for showing the retrieved and failed claims on the screen:

   Claims("Received claims", credential.claims)
   Spacer(Modifier.padding(8.dp))
   Claims("Failed claims", credential.claimErrors)

10. Add the following code under the // Verify mDocs - Step 4.10: Show credential verification status comment to show the overall verification status:

    val statusStyle = MaterialTheme.typography.titleLarge
    if (credential.verificationResult.verified) {
        Text("Verified", style = statusStyle, color = Color.Green)
    } else {
        Text("Not verified", style = statusStyle, color = Color.Red)
    }