Skip to content

[MS-1065] Adding 'metadata' field to the ConfirmationCalloutEventV3#1262

Merged
alexandr-simprints merged 2 commits into
release/2025.2.0from
MS-1065-android-add-metadata-field-to-the-confirmation-callout-2
Jul 14, 2025
Merged

[MS-1065] Adding 'metadata' field to the ConfirmationCalloutEventV3#1262
alexandr-simprints merged 2 commits into
release/2025.2.0from
MS-1065-android-add-metadata-field-to-the-confirmation-callout-2

Conversation

@alexandr-simprints
Copy link
Copy Markdown
Contributor

JIRA ticket
Will be released in: 2025.2.0

Notable changes

  • The ConfirmationCalloutEventV3 class now contains metadata: String? field
  • This field already exists in the confirmation callout request, and now is passed to the event
  • The metadata field is now also passed to the BFSID

Testing guidance

  • Send the metadata=test field for the com.simprints.id.CONFIRM_IDENTITY request. Use the Custom Intent screen within the Intent Launcher app for that.

Additional work checklist

  • Effect on other features and security has been considered
  • Test cases in Testiny are up to date (ticket)
  • Other teams notified about the changes (BFSID on dev is ready)

@sonarqubecloud
Copy link
Copy Markdown

@alexandr-simprints alexandr-simprints merged commit ed29476 into release/2025.2.0 Jul 14, 2025
12 checks passed
@alexandr-simprints alexandr-simprints deleted the MS-1065-android-add-metadata-field-to-the-confirmation-callout-2 branch July 14, 2025 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants