Update reverification docs#3394
Open
alexisintech wants to merge 4 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
@alexisintech just checking, this is ready for review? It's still in draft but got a review request email. |
Member
Author
i reverted it to draft - its waiting on some expo stuff |
useReverification error handling examples
Member
Author
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Member
Author
|
Pushed some changes directly in 51fe646.
|
alexisintech
commented
Jun 11, 2026
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.

🔎 Previews:
What does this solve?
While working on the update-password custom flow, I noticed the reverification docs were incorrect. The
isReverificationCancelledErrorwas being imported fromclerk/shared, which users are advised against doing per this Slack discussion. This was incorrect anyways, because it's re-exported from the appropriate SDK's, so importing fromclerk/sharedwasn't necessary. Also, drops support for Expo as it does not support theuseReverification()hook opening a modal (talked with Mike to add reverification work to the mobile team's radar).What changed?
docs/reference/hooks/use-reverification.mdx:isClerkRuntimeError(e) &&guard from cancellation checks —isReverificationCancelledErroralready narrows correctly on its own, matching the canonical usage in theuseReverificationJSDoc inclerk/javascript.react-routerandtanstack-react-startexamples from importingisReverificationCancelledErrorout of@clerk/sharedto the SDK's own/errorssubpath (@clerk/react-router/errors,@clerk/tanstack-react-start/errors), aligning them with thereactandnextjsexamples.importandcatchbranch from thechrome-extensionexamples, since@clerk/chrome-extensiondoes not expose an./errorssubpath export.useReverification()doesn't open the modal on native Expo.docs/guides/secure/reverification.mdx:<If sdk="ruby">. It adds an<If sdk="nextjs"wrapper around an example for performing reverification in Server Actions.useReverification()examples instead of duplicating them.docs/reference/ruby/overview.mdx:Deadline
Other resources
Relevant Slack conversation regarding error helpers