Repository navigation
Swift demo: hashed IDs, identify from URL, profile id/neighbors and async/await - #93
Merged
Merged
Conversation
The Swift demo only showed plaintext identify and completion-handler targeting. Add: - Identify screen: an "Identify (hashed email)" button sending .hem, and a URL field plus "Identify from URL" button calling tryIdentifyFromURL with a sample newsletter link carrying an oeid. - Prebid screen: targeting via async/await; the GAM screen keeps the completion handler, so both styles are shown. - Both banner screens: profile() also passes an id and neighbors, built with .extendedIdentifier. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mosherBT
approved these changes
Nov 9, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Why
The usage guides document hashed identifiers,
tryIdentifyFromURL,profileid/neighborsand the async/await API, but the Swift demo showed none of them: only plaintextidentifyand completion-handlertargeting.