feat(web2app): DEV-847 Android SDK redemption surface#812
Open
shameondev wants to merge 2 commits into
Open
Conversation
Per plan §Mobile SDK API surface and §DEV-847: - handleRedemptionLink(uri:callback:) — AL email->app entry; POSTs /v4/web/redeem - presentReissueUI(activity:onCompletion:) — fallback email-input UI; POSTs /v4/web/redeem/reissue - 5-case RedemptionResult enum (mirrors iOS) - 409 handling via POST /v4/web/redeem/status + identify-flow recovery (RT4-W2) - Sample manifest updated: App Links (https + autoVerify=true) for email links - DROP qonversion://redeem registration as email transport (hijack vector per RT2-W3) Custom qonversion:// scheme remains only for host-app->SDK in-process forwarding.
RT2-W3 — App Links only as email-link transport RedemptionManager.extractToken now requires the URI scheme to be literally "https" (App Link with android:autoVerify="true") and rejects everything else BEFORE any token extraction or network call. Previously any blank-scheme guard let the custom `qonversion://` form through, allowing an installed app that registers the scheme in its intent-filter to hijack the redemption token. The custom scheme is reserved for in-process host→SDK forwarding and is not exercised by this entry point. RT5-N2 — identify() launch contract New QProductCenterManagerIdentifyContractTest pins the behaviour that QProductCenterManager.processIdentity calls launchResultCache.clearPermissionsCache + launch(RequestTrigger.Identify) on the cross-user branch (QProductCenterManager.kt:221-257). The web→app recovery flow described in r8-overview §"POST /v4/web/redeem/status" relies on this — sign-in must trigger a fresh entitlement fetch via the merged identity. Any future change that defers or skips the launch will now fail CI. Sample app bundled M1 work: * MainActivity adds intent-filter handling + Qonversion.handleRedeem demo wiring for end-to-end QA of the deep-link flow. * AndroidManifest declares the verified App Link intent-filter. * build.gradle adds the sample-app dependency on the SDK. Tests added: scheme rejection unit tests + 5 contract tests.
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
1 participant
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.
DEV-847 (Web 2 App M1 — Mobile SDK).
Public API added
Behavior
Security (RT2-W3 + RT-F11)
Build + tests
Test coverage: Uri parsing (valid/malformed/prefix-only), 200/404/410/409/network → result mapping, RT5-N2 identify contract.
Test plan
Refs: plan §Mobile SDK API surface → Android, §DEV-847 (M1.5), RT2-W3, RT5-N2