Skip to content

FENCE-3194: Wire response encryption into example - #605

Merged
alanjcharles14 merged 2 commits into
masterfrom
alancharles/fence-3194-response-format-example
Nov 18, 2026
Merged

alanjcharles14 merged 2 commits into
masterfrom
alancharles/fence-3194-response-format-example

Conversation

@alanjcharles14

Copy link
Copy Markdown
Contributor

Summary

Updates the Example app to display JWS, JWE, and ID responses consistently and provide copyable backend relay JSON containing only available token and _id fields.

Adds token-cache clearing, continuous-token logging, and correct beacon availability reporting for reduced responses. SDK production code is unchanged.

Linear ticket (Radar internal)

FENCE-3194

Related issue

Stacked on the Android SDK response-format PR.
iOS Example PR #801

Type of change

  • Documentation / internal only (no SDK behavior change)

Manual test steps

Server QA pending:

  1. Run the Example app and exercise Track and Reveal with each server-selected format.
  2. Inspect response metadata and long-press a result to copy its backend relay JSON.
  3. Start continuous verified tracking and confirm token updates appear in the logs.
  4. Clear the token cache between server format changes and request a fresh result.

Local validation: Example debug build and lint passed, with no new lint warnings. SDK ktlint and Android lint passed. Device/UI QA remains pending.

Checklist

  • Unit tests not applicable; Example-only changes
  • ./gradlew :sdk:ktlintCheck and ./gradlew :sdk:lintDebug pass locally
  • No SDK public API changes requiring migration or version updates
  • No real API keys committed in the example app
  • Changes are scoped to Example behavior

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues are recorded for the Android example response-handling and relay-copying changes.

No open issues 🎉

What changed in this PR

Updates the Android Example app to present JWS, JWE, and ID verification responses consistently and support backend relay copying. SDK production code remains unchanged.

Changes:

  • Centralizes response metadata, relay JSON, and format-aware beacon availability reporting.
  • Adds token-cache clearing and consistent logging for continuous token updates.
  • Adds a long-press menu to copy available token and _id fields.
File Description
example/​src/​main/​java/​io/​radar/​example/​tests/​panels/​VerifiedPanel.kt Uses shared response logging and adds token-cache clearing.
example/​src/​main/​java/​io/​radar/​example/​store/​VerifiedResponse.kt Formats response details, beacon availability, and backend relay JSON.
example/​src/​main/​java/​io/​radar/​example/​store/​LogStore.kt Centralizes verified-response logging and attaches relay payloads.
example/​src/​main/​java/​io/​radar/​example/​store/​ConsoleEntry.kt Adds optional relay JSON to console entries.
example/​src/​main/​java/​io/​radar/​example/​MainActivity.kt Routes continuous token updates through shared response logging.
example/​src/​main/​java/​io/​radar/​example/​console/​ConsoleEntryRow.kt Adds a long-press menu for copying backend relay JSON.

Review effort: Balanced

Base automatically changed from alancharles/fence-3194-android-add-jwe-encryption-for-fraud to master November 18, 2026 19:47
@alanjcharles14
alanjcharles14 force-pushed the alancharles/fence-3194-response-format-example branch from c885805 to 894ca80 Compare November 18, 2026 19:47
@alanjcharles14
alanjcharles14 merged commit 283c2ce into master Nov 18, 2026
1 check was pending
@alanjcharles14
alanjcharles14 deleted the alancharles/fence-3194-response-format-example branch November 18, 2026 19:48
@alanjcharles14 alanjcharles14 mentioned this pull request Nov 18, 2026
7 of 10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants