Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughThis PR updates documentation across SDK and onchain integration guides with minor punctuation fixes, corrected internal links, and comprehensive restructuring of onchain integration documentation. The onchain integration guides are reorganized from concise "Flow" sections into detailed "Implementation Flow" sections with explicit SDK references and new "Next Steps" guidance. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In @content/docs/onchain/stellar/index.mdx:
- Around line 6-27: Update the "Next Steps" section in
content/docs/onchain/stellar/index.mdx to explicitly reference the Stellar
quickstart guide by linking to quickstart.mdx (e.g., "See the Stellar quickstart
for Soroban contract setup, CLI deployment, and Freighter wallet
configuration"), so Stellar developers can navigate from the high-level
Implementation Flow directly to chain-specific setup instructions.
🧹 Nitpick comments (9)
content/docs/onchain/gear/index.mdx (2)
14-24: Documentation lacks Gear-specific implementation details.The implementation steps are generic and don't include any Gear-specific guidance such as:
- Smart contract code examples for Gear's Actor model
- Gear-specific serialization/deserialization patterns
- Links to example Gear contracts or templates
This may be intentional to align with the standardized pattern across on-chain docs, but users looking for Gear integration will need more concrete examples to implement verification.
Consider adding a link to Gear-specific contract examples or a reference implementation, similar to how other blockchain-specific docs might reference their respective contract templates.
26-27: Next Steps could be more actionable.The "Next Steps" section refers users back to SDK documentation, but for an on-chain integration guide, it would be more helpful to also link to:
- Gear-specific contract deployment guides
- Example repositories demonstrating the full integration
- Reclaim's verifier contract addresses on Gear (if deployed)
content/docs/onchain/diamante/index.mdx (1)
24-26: Minor: Trailing whitespace on line 25.There appears to be trailing whitespace before the "Next Steps" section. While minor, removing it maintains consistency with the other onchain documentation files.
Suggested fix
4. **Verify On-Chain** - Execute the verification process within your smart contract - Handle the verification result according to your application logic - + ### Next Stepscontent/docs/onchain/mina/index.mdx (1)
6-27: Documentation follows the standardized structure.The Implementation Flow section is well-organized and consistent with other onchain documentation.
Optional terminology consideration: Mina's ecosystem typically refers to "zkApps" rather than "smart contracts." Consider updating lines 20 and 23 to use "zkApp" for more precise Mina-specific terminology, though "smart contract" is widely understood.
📝 Optional: Use Mina-specific terminology
3. **Submit for Verification** - Transform the proof into its serialized format - - Submit the serialized proof to your designated smart contract + - Submit the serialized proof to your designated zkApp 4. **Verify On-Chain** - - Execute the verification process within your smart contract + - Execute the verification process within your zkApp - Handle the verification result according to your application logiccontent/docs/onchain/sui/index.mdx (1)
6-27: Documentation structure looks good.The new Implementation Flow section provides a clear, consistent structure that aligns with other onchain documentation. The four-step process and SDK references (
/js-sdk/installation,/react-native/installation,/flutter/installation) are well-organized and properly linked.Unlike the Aleph Zero docs, this file lacks an Overview section. Consider adding a brief overview for consistency across onchain documentation, though this is optional.
content/docs/onchain/fuel/index.mdx (1)
6-27: Consider adding an Overview section for consistency.The Aptos and Cardano documentation files include an "Overview" section that provides context before the Implementation Flow. This file (and Polkadot, Solidity) lacks this section, creating inconsistency across the onchain documentation.
Consider adding a brief Overview section similar to:
### Overview The Reclaim Protocol allows you to verify user data proofs on the Fuel blockchain. This integration enables decentralized verification of user-provided proofs through smart contracts.content/docs/onchain/polkadot/index.mdx (1)
6-27: Structure is consistent with the PR's standardization effort.The Implementation Flow and Next Steps sections are well-structured. Same note as the Fuel file: consider adding an "Overview" section for consistency with Aptos and Cardano documentation.
content/docs/onchain/solidity/index.mdx (1)
6-27: LGTM with optional enhancement.The standardized Implementation Flow structure is clear and actionable. For Solidity specifically, an Overview section could be valuable to mention EVM compatibility and the broader applicability across EVM-compatible chains.
content/docs/onchain/index.mdx (1)
7-9: Unused icon imports.The icons
Server,Code2, andSmartphoneare imported but not used in any of the Card components. These appear to be leftover from previous cards that were replaced.🧹 Remove unused imports
import { Card, Cards } from 'fumadocs-ui/components/card' -import Server from 'lucide-react/dist/esm/icons/server' -import Code2 from 'lucide-react/dist/esm/icons/code-2' -import Smartphone from 'lucide-react/dist/esm/icons/smartphone' import Boxes from 'lucide-react/dist/esm/icons/boxes'
📜 Review details
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (23)
content/docs/android/usage.mdxcontent/docs/ios-swift/usage.mdxcontent/docs/js-sdk/generating-proof.mdxcontent/docs/js-sdk/installation.mdxcontent/docs/onchain/alephzero/index.mdxcontent/docs/onchain/aptos/index.mdxcontent/docs/onchain/cardano/index.mdxcontent/docs/onchain/cosmos/index.mdxcontent/docs/onchain/diamante/index.mdxcontent/docs/onchain/fuel/index.mdxcontent/docs/onchain/gear/index.mdxcontent/docs/onchain/index.mdxcontent/docs/onchain/lukso/index.mdxcontent/docs/onchain/mina/index.mdxcontent/docs/onchain/near/index.mdxcontent/docs/onchain/polkadot/index.mdxcontent/docs/onchain/solana/index.mdxcontent/docs/onchain/solidity/index.mdxcontent/docs/onchain/starknet/index.mdxcontent/docs/onchain/stellar/index.mdxcontent/docs/onchain/sui/index.mdxcontent/docs/onchain/xion/index.mdxcontent/docs/react-native/install/expo.mdx
🧰 Additional context used
🧠 Learnings (11)
📚 Learning: 2025-12-03T01:18:34.283Z
Learnt from: CR
Repo: reclaimprotocol/docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-03T01:18:34.283Z
Learning: Applies to **/app.json : Add reclaimprotocol/inapp-rn-sdk plugin to app.json plugins array for React Native Expo projects
Applied to files:
content/docs/react-native/install/expo.mdx
📚 Learning: 2025-12-03T01:18:34.283Z
Learnt from: CR
Repo: reclaimprotocol/docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-03T01:18:34.283Z
Learning: Applies to **/*.{js,jsx,ts,tsx} : Use ReclaimProofRequest.init(APP_ID, APP_SECRET, PROVIDER_ID) before calling triggerReclaimFlow() in frontend code
Applied to files:
content/docs/react-native/install/expo.mdxcontent/docs/onchain/sui/index.mdxcontent/docs/onchain/xion/index.mdxcontent/docs/onchain/mina/index.mdxcontent/docs/onchain/solana/index.mdxcontent/docs/onchain/stellar/index.mdxcontent/docs/onchain/polkadot/index.mdxcontent/docs/onchain/alephzero/index.mdxcontent/docs/onchain/fuel/index.mdxcontent/docs/onchain/lukso/index.mdxcontent/docs/android/usage.mdxcontent/docs/onchain/cosmos/index.mdxcontent/docs/js-sdk/generating-proof.mdxcontent/docs/onchain/aptos/index.mdxcontent/docs/onchain/diamante/index.mdxcontent/docs/onchain/near/index.mdxcontent/docs/onchain/cardano/index.mdxcontent/docs/onchain/gear/index.mdxcontent/docs/ios-swift/usage.mdxcontent/docs/js-sdk/installation.mdxcontent/docs/onchain/solidity/index.mdxcontent/docs/onchain/starknet/index.mdx
📚 Learning: 2025-12-03T01:18:34.283Z
Learnt from: CR
Repo: reclaimprotocol/docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-03T01:18:34.283Z
Learning: Applies to **/*.{js,ts}|**/*.py : Call ReclaimProofRequest.verifyProof(claimData) on received proofs to validate proof authenticity
Applied to files:
content/docs/onchain/sui/index.mdxcontent/docs/onchain/xion/index.mdxcontent/docs/onchain/mina/index.mdxcontent/docs/onchain/solana/index.mdxcontent/docs/onchain/stellar/index.mdxcontent/docs/onchain/polkadot/index.mdxcontent/docs/onchain/alephzero/index.mdxcontent/docs/onchain/fuel/index.mdxcontent/docs/onchain/lukso/index.mdxcontent/docs/onchain/cosmos/index.mdxcontent/docs/js-sdk/generating-proof.mdxcontent/docs/onchain/aptos/index.mdxcontent/docs/onchain/diamante/index.mdxcontent/docs/onchain/near/index.mdxcontent/docs/onchain/cardano/index.mdxcontent/docs/onchain/gear/index.mdxcontent/docs/js-sdk/installation.mdxcontent/docs/onchain/solidity/index.mdxcontent/docs/onchain/starknet/index.mdx
📚 Learning: 2025-12-03T01:18:34.283Z
Learnt from: CR
Repo: reclaimprotocol/docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-03T01:18:34.283Z
Learning: Applies to **/*.{js,jsx,ts,tsx} : Call Reclaim.verifySignedProof() before using proof data to ensure cryptographic validity
Applied to files:
content/docs/onchain/sui/index.mdxcontent/docs/onchain/xion/index.mdxcontent/docs/onchain/mina/index.mdxcontent/docs/onchain/solana/index.mdxcontent/docs/onchain/stellar/index.mdxcontent/docs/onchain/polkadot/index.mdxcontent/docs/onchain/alephzero/index.mdxcontent/docs/onchain/lukso/index.mdxcontent/docs/onchain/cosmos/index.mdxcontent/docs/js-sdk/generating-proof.mdxcontent/docs/onchain/aptos/index.mdxcontent/docs/onchain/diamante/index.mdxcontent/docs/onchain/near/index.mdxcontent/docs/onchain/cardano/index.mdxcontent/docs/onchain/gear/index.mdxcontent/docs/js-sdk/installation.mdxcontent/docs/onchain/solidity/index.mdxcontent/docs/onchain/starknet/index.mdx
📚 Learning: 2025-12-03T01:18:34.283Z
Learnt from: CR
Repo: reclaimprotocol/docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-03T01:18:34.283Z
Learning: Coordinate development flow starting with frontend quickstart, then backend verification, then error handling
Applied to files:
content/docs/onchain/mina/index.mdxcontent/docs/onchain/polkadot/index.mdxcontent/docs/onchain/lukso/index.mdxcontent/docs/onchain/aptos/index.mdxcontent/docs/onchain/near/index.mdxcontent/docs/onchain/cardano/index.mdxcontent/docs/js-sdk/installation.mdxcontent/docs/onchain/starknet/index.mdx
📚 Learning: 2025-12-03T01:18:34.283Z
Learnt from: CR
Repo: reclaimprotocol/docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-03T01:18:34.283Z
Learning: Applies to **/*.{js,jsx,ts,tsx} : Implement startSession with onSuccess and onError callbacks to handle ReclaimProofRequest completion
Applied to files:
content/docs/onchain/alephzero/index.mdx
📚 Learning: 2025-12-03T01:18:34.283Z
Learnt from: CR
Repo: reclaimprotocol/docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-03T01:18:34.283Z
Learning: Production deployment requires backend proof verification, secure credential management, webhook implementation, error tracking, and rate limiting
Applied to files:
content/docs/onchain/alephzero/index.mdxcontent/docs/js-sdk/installation.mdx
📚 Learning: 2025-12-03T01:18:34.283Z
Learnt from: CR
Repo: reclaimprotocol/docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-03T01:18:34.283Z
Learning: Applies to **/*.{js,jsx,ts,tsx} : Implement proper error handling for ReclaimProofRequest operations including onError callbacks
Applied to files:
content/docs/onchain/alephzero/index.mdx
📚 Learning: 2025-12-03T01:18:34.283Z
Learnt from: CR
Repo: reclaimprotocol/docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-03T01:18:34.283Z
Learning: Applies to **/*.{js,ts}|**/*.py : Always verify proofs server-side in production - do not rely on client-side verification
Applied to files:
content/docs/onchain/alephzero/index.mdx
📚 Learning: 2025-12-03T01:18:34.283Z
Learnt from: CR
Repo: reclaimprotocol/docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-03T01:18:34.283Z
Learning: Show clear verification status, provide fallback options, handle edge cases gracefully, and optimize for mobile experience in user-facing applications
Applied to files:
content/docs/onchain/alephzero/index.mdx
📚 Learning: 2025-12-03T01:18:34.283Z
Learnt from: CR
Repo: reclaimprotocol/docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-03T01:18:34.283Z
Learning: Applies to **/*.{js,jsx,ts,tsx,py} : Use environment variables for APP_ID, APP_SECRET, and PROVIDER_ID credentials
Applied to files:
content/docs/android/usage.mdxcontent/docs/ios-swift/usage.mdx
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Cursor Bugbot
🔇 Additional comments (20)
content/docs/android/usage.mdx (1)
25-25: LGTM!Minor punctuation fix for consistency across documentation.
content/docs/js-sdk/generating-proof.mdx (1)
7-7: LGTM!Good correction to use the full path
/js-sdk/preparing-request, which is consistent with the link on line 19 and ensures reliable navigation regardless of URL context.content/docs/ios-swift/usage.mdx (1)
26-26: LGTM!Minor punctuation fix for consistency, matching the similar update in the Android documentation.
content/docs/react-native/install/expo.mdx (1)
92-92: Link anchor is valid. The#basic-usageanchor exists in the target installation file (generated from the "## Basic Usage" heading).content/docs/js-sdk/installation.mdx (1)
33-33: Link target verified as correct.The file
content/docs/js-sdk/verifying-proofs.mdxexists and the link in line 33 properly references it with the plural formverifying-proofs.content/docs/onchain/gear/index.mdx (1)
8-12: The SDK documentation links are valid and properly formatted. All three SDK installation pages exist at the referenced locations:
/js-sdk/installation→content/docs/js-sdk/installation.mdx✓/react-native/installation→content/docs/react-native/installation.mdx✓/flutter/installation→content/docs/flutter/installation.mdx✓The root-relative path format used is standard for documentation systems and requires no changes.
Likely an incorrect or invalid review comment.
content/docs/onchain/cosmos/index.mdx (3)
14-24: Flow steps are well-structured.The verification flow is logically ordered and clearly explained.
Consider whether Cosmos-specific details would be valuable here (e.g., CosmWasm contract snippets, message formats, or links to example contracts). However, if the intent is to keep this as a high-level overview with SDK docs providing implementation details, the current approach is appropriate.
26-27: Good addition of navigation guidance.The "Next Steps" section provides clear direction for users to continue their implementation journey.
6-12: LGTM! Clear structure with valid SDK references.The renamed heading and explicit SDK links provide clear guidance for developers. All three SDK installation paths are valid and accessible.
content/docs/onchain/near/index.mdx (1)
6-27: LGTM!The documentation maintains consistency with other onchain integration guides. The implementation flow is clear and provides a good starting point for developers.
content/docs/onchain/starknet/index.mdx (1)
6-27: LGTM!Documentation structure aligns with the broader onchain integration pattern. Clear and consistent formatting.
content/docs/onchain/xion/index.mdx (1)
6-27: LGTM!The documentation follows the established pattern and provides clear guidance for XION integration.
content/docs/onchain/alephzero/index.mdx (2)
13-13: SDK reference update looks correct.Changing from "Reclaim React SDK" to "Reclaim JS SDK" for web and backend implementations is appropriate. The JS SDK is the correct choice for general web and backend use cases, while React Native SDK remains for mobile applications.
29-30: Next Steps simplification is consistent with other docs.The condensed Next Steps section aligns with the standardized format being applied across other onchain documentation in this PR.
content/docs/onchain/solana/index.mdx (1)
6-27: Implementation flow documentation is well-structured.The standardized Implementation Flow section provides clear guidance for Solana integration. The structure is consistent with other onchain documentation in this PR.
content/docs/onchain/lukso/index.mdx (1)
6-27: Documentation structure is consistent and appropriate for Lukso.The Implementation Flow section follows the standardized format and the terminology ("smart contract") is accurate for Lukso's EVM-compatible architecture.
content/docs/onchain/cardano/index.mdx (1)
9-30: Well-structured documentation update.This file represents the ideal structure for onchain documentation with the Overview, Implementation Flow, and Next Steps sections. The SDK references and four-step flow provide clear implementation guidance. Based on learnings, the flow correctly guides developers from frontend SDK integration through to on-chain verification.
content/docs/onchain/aptos/index.mdx (1)
9-30: Documentation structure is solid with verified SDK links.The restructured "Implementation Flow" with explicit SDK references and the new "Next Steps" section provides clear guidance for developers. All three SDK documentation links are valid—the JS SDK, React Native SDK, and Flutter SDK installation pages exist and are correctly referenced. The four-step flow aligns well with the recommended development pattern (frontend quickstart → backend verification → on-chain handling).
content/docs/onchain/index.mdx (2)
94-123: Existing cards reorganized appropriately.Solana, Solidity, Stellar, and Sui cards have been updated with consistent formatting and proper alphabetical placement. The hrefs and descriptions follow the established pattern.
28-81: All blockchain cards are properly structured with alphabetical ordering and consistent formatting.Documentation pages exist for all entries: Aleph Zero, Aptos, Cardano, Cosmos, Diamante, Fuel, Gear, Lukso, and Mina. Icon reuse:
Globe2for Cosmos and Diamante;Blocksfor Fuel, Mina, and XION. If visual distinction between chains is desired, consider using unique icons for each.Likely an incorrect or invalid review comment.
| ### Implementation Flow | ||
|
|
||
| 1. **Request Proofs** | ||
| - Implement proof requests in your application using one of our official SDKs: | ||
| - [Reclaim JS SDK](/js-sdk/installation) for web and backend implementations | ||
| - [Reclaim React Native SDK](/react-native/installation) for mobile applications | ||
| - [Reclaim Flutter SDK](/flutter/installation) for cross-platform applications | ||
|
|
||
| 2. **Handle Proof Upload** | ||
| - Once the user successfully uploads their proof, store the proof identifier | ||
| - Maintain proper record-keeping for subsequent verification | ||
|
|
||
| 3. **Submit for Verification** | ||
| - Transform the proof into its serialized format | ||
| - Submit the serialized proof to your designated smart contract | ||
|
|
||
| 4. **Verify On-Chain** | ||
| - Execute the verification process within your smart contract | ||
| - Handle the verification result according to your application logic | ||
|
|
||
| ### Next Steps | ||
| After understanding the basic flow, refer to our specific SDK documentation for detailed implementation guidelines and best practices. |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check the directory structure
echo "=== Documentation root structure ==="
ls -la content/docs/ 2>/dev/null | head -20
echo -e "\n=== Looking for SDK documentation ==="
fd -t d "js-sdk|react-native|flutter" content/docs/ 2>/dev/null
echo -e "\n=== Checking for installation files ==="
fd -t f -e mdx "installation" content/docs/ 2>/dev/null | head -20
echo -e "\n=== Looking for Stellar/Soroban references ==="
fd -t f -e mdx . content/docs/ 2>/dev/null | xargs grep -l "Soroban\|Stellar" 2>/dev/null | head -10Repository: reclaimprotocol/docs
Length of output: 1641
🏁 Script executed:
#!/bin/bash
# Check if the specific SDK paths exist
echo "=== Checking SDK documentation paths ==="
test -d "content/docs/js-sdk" && echo "✓ js-sdk directory exists" || echo "✗ js-sdk directory missing"
test -d "content/docs/react-native" && echo "✓ react-native directory exists" || echo "✗ react-native directory missing"
test -d "content/docs/flutter" && echo "✓ flutter directory exists" || echo "✗ flutter directory missing"
echo -e "\n=== Checking for installation files ==="
test -f "content/docs/js-sdk/installation.mdx" && echo "✓ js-sdk/installation.mdx exists" || echo "? js-sdk/installation.mdx not found"
test -f "content/docs/react-native/installation.mdx" && echo "✓ react-native/installation.mdx exists" || echo "? react-native/installation.mdx not found"
test -f "content/docs/flutter/installation.mdx" && echo "✓ flutter/installation.mdx exists" || echo "? flutter/installation.mdx not found"
echo -e "\n=== Full content/docs structure ==="
find content/docs -maxdepth 2 -type d | sortRepository: reclaimprotocol/docs
Length of output: 1235
🏁 Script executed:
#!/bin/bash
# Read the actual stellar index.mdx file
echo "=== Stellar index.mdx content ==="
cat -n content/docs/onchain/stellar/index.mdx
echo -e "\n=== Stellar quickstart.mdx (first 50 lines) ==="
head -50 content/docs/onchain/stellar/quickstart.mdx
echo -e "\n=== Check for Soroban references ==="
grep -n "Soroban\|soroban" content/docs/onchain/stellar/*.mdx 2>/dev/null || echo "No Soroban references found"Repository: reclaimprotocol/docs
Length of output: 4493
🏁 Script executed:
#!/bin/bash
# Check the directory structure of related documentation
echo "=== Files in stellar directory ==="
ls -la content/docs/onchain/stellar/
echo -e "\n=== Files in onchain/index.mdx for blockchain nav ==="
head -100 content/docs/onchain/index.mdx | grep -A 5 -B 5 "stellar\|Stellar" || echo "Checking onchain index..."Repository: reclaimprotocol/docs
Length of output: 417
SDK links are valid; consider referencing the Stellar quickstart guide in Next Steps.
The restructured Implementation Flow is clear and well-organized. All SDK documentation links are valid:
- ✓
/js-sdk/installation - ✓
/react-native/installation - ✓
/flutter/installation
Stellar-specific guidance already exists in the quickstart.mdx file (Soroban contract setup, CLI deployment, Freighter wallet configuration). The "Next Steps" section could explicitly reference this quickstart for Stellar developers seeking detailed implementation guidance, improving navigation for chain-specific workflows.
🤖 Prompt for AI Agents
In @content/docs/onchain/stellar/index.mdx around lines 6 - 27, Update the "Next
Steps" section in content/docs/onchain/stellar/index.mdx to explicitly reference
the Stellar quickstart guide by linking to quickstart.mdx (e.g., "See the
Stellar quickstart for Soroban contract setup, CLI deployment, and Freighter
wallet configuration"), so Stellar developers can navigate from the high-level
Implementation Flow directly to chain-specific setup instructions.
Note
Aligns onchain docs and navigation, plus small link/copy fixes across SDK guides.
Implementation Flowwith "Next Steps" (Alephzero, Aptos, Cardano, Cosmos, Diamante, Fuel, Gear, Lukso, Mina, NEAR, Polkadot, Solana, Solidity, Starknet, Stellar, Sui, XION)onchain/index.mdxcards: reordered and expanded entries (e.g., Aleph Zero, Aptos, Cardano, Diamante, Fuel, Gear, Lukso, Mina, NEAR, Polkadot, Solana, Solidity, Starknet, Stellar, Sui, XION) with iconsgenerating-proofnow references/js-sdk/preparing-request;installationnow points toverifying-proofsandroid/usage.mdx,ios-swift/usage.mdx, and Expo guide link anchor inreact-native/install/expo.mdxWritten by Cursor Bugbot for commit 2f99736. This will update automatically on new commits. Configure here.
Summary by CodeRabbit
Documentation
✏️ Tip: You can customize this high-level summary in your review settings.