Release to Production v2.9.29 - 2026-09-06 - #2296
Merged
Merged
Conversation
…faucet notice on the KYC flow (#2288) Store review - Ask for a store rating through the native in-app review sheet (expo-store-review) instead of a custom dialog, as Apple and Google guidelines require. - Prompt only after the user acknowledges a verified proof, and only once Home has settled, never on the proof screen or over a Modal route. - Local policy mirrors the OS quotas so every request counts: 2 successful proofs before the first prompt, 5 more between prompts, 90-day cooldown, 3 prompts per rolling year, and a 24h hold after any failed proof. - Persisted counters live in a dedicated zustand store; the armed flag is session-only so a killed app never resurrects a stale prompt. KYC / Didit faucet notice - Every Didit launch (launcher hook, chip-symbol "No" on logo confirmation, and the SDK ID-picker "kyc" selection) now shows an explicit notice that third-party verified IDs are not compatible with the Google USAT mainnet faucet, with Continue anyway / Go back. - The notice reuses the single FeedbackProvider AlertModal where one is already on screen, and a store-driven modal at the navigation root for the provider path that sits above FeedbackProvider. - New analytics: KYC faucet notice shown/continued/declined and App: Store Review Requested. Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
feat(app): store review prompt after verified proofs and Google USAT …
The first verified proof is the strongest moment in the product and many users never do a second one, so waiting for two proofs threw away most of the reach. The 90-day cooldown, the 3-per-year cap and the 24h failure hold are unchanged. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…roof fix(app): request the store review after the first verified proof
Update build numbers, platform build files, and deployment timestamps after successful deployment. Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
) The first verified proof is the strongest moment in the product and many users never do a second one, so waiting for two proofs threw away most of the reach. The 90-day cooldown, the 3-per-year cap and the 24h failure hold are unchanged. Co-authored-by: turnoffthiscomputer <colin.remi07@gmail.com> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
Update build numbers, platform build files, and deployment timestamps after successful deployment. Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…ch (#2291) * chore(app): temporarily disable the KYC/Didit flow behind a kill switch Adds KYC_FLOW_ENABLED (false) in integrations/kyc/constants and routes every Didit entry point through it. Nothing is removed; flipping the constant back to true restores the previous behaviour. Entry points gated - ID picker: the "View other supported IDs (BETA)" footer is hidden via a new optional showKycOption prop on the SDK IDSelection screen; the provider also drops 'kyc' from a country's document types and sends the user to ComingSoon when nothing else remains, and a stray 'kyc' selection goes to ComingSoon. - useKycLauncher: isKycAvailable=false, launchKycVerification no-ops, and showKycFallbackModal runs the dismiss handler directly so Cancel on the camera, NFC scan and onboarding screens still navigates as before. - "Try Alternative Verification" hidden on the camera and NFC trouble screens, the NFC scan screen (unsupported/disabled NFC) and the data confirmation screen; "Try a different method" hidden on the NFC/MRZ registration fallback and Aadhaar upload error screens; the camera-permission alert no longer offers the KYC fallback. - Logo confirmation "No": shows a plain "Document Not Supported" notice instead of redirecting to the external verifier. Left untouched on purpose: pending-KYC recovery, KYC result notifications, KycSuccess/KycFailure screens and existing KYC ID cards, so in-flight and already-registered verifications keep working. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * fix(app): honest copy and routing when the KYC flow is disabled (review follow-ups) - Camera-unavailable alert no longer promises an alternative verification method when no fallback is offered. - A kyc_result "retry" notification routes to the terminal KycFailure state instead of CountryPicker, which no longer offers KYC under the kill switch. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
chore: sync dev build numbers (iOS 241 / Android 173) into staging
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
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
3 participants
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.
🎯 Production Release
Release Date: September 06, 2026
Commits ahead: 9
This automated PR promotes tested changes from
stagingtomainfor production deployment.What's Included
All changes that have been verified in the staging environment.
Note: This PR is directly from
staging, so new commits merged tostagingwill automatically appear here.Pre-Deployment Checklist
Deployment Notes
Merging this PR will trigger production deployment.
This PR was automatically created by the Release Calendar workflow on September 06, 2026