Skip to content

added troubeshooting page, fixed 404 page layout issue and updated fa… #99

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Sajjad21990 merged 1 commit into from
Jan 21, 2026
Merged

added troubeshooting page, fixed 404 page layout issue and updated fa… #99

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions app/(home)/not-found.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
import Link from 'next/link';

export default function NotFound() {
return (
<div
className="fixed inset-0 flex flex-col items-center justify-center"
style={{ zIndex: 9999, backgroundColor: '#f5f5f5' }}
>
<div className="dark:hidden absolute inset-0" style={{ backgroundColor: '#f5f5f5' }} />
<div className="hidden dark:block absolute inset-0" style={{ backgroundColor: '#0a0a0a' }} />
<div className="relative flex flex-col items-center">
<h1 className="text-8xl font-bold text-neutral-900 dark:text-neutral-100">404</h1>
<p className="mt-4 text-xl text-neutral-600 dark:text-neutral-400 text-center">
This page could not be found.
</p>
<Link
href="/"
className="mt-8 px-6 py-3 rounded-md bg-neutral-900 dark:bg-neutral-100 text-white dark:text-neutral-900 hover:opacity-90 transition-opacity font-medium"
>
Go back home
</Link>
</div>
</div>
);
}
25 changes: 25 additions & 0 deletions app/not-found.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
import Link from 'next/link';

export default function NotFound() {
return (
<div
className="fixed inset-0 flex flex-col items-center justify-center"
style={{ zIndex: 9999, backgroundColor: '#f5f5f5' }}
>
<div className="dark:hidden absolute inset-0" style={{ backgroundColor: '#f5f5f5' }} />
<div className="hidden dark:block absolute inset-0" style={{ backgroundColor: '#0a0a0a' }} />
<div className="relative flex flex-col items-center">
<h1 className="text-8xl font-bold text-neutral-900 dark:text-neutral-100">404</h1>
<p className="mt-4 text-xl text-neutral-600 dark:text-neutral-400 text-center">
This page could not be found.
</p>
<Link
href="/"
className="mt-8 px-6 py-3 rounded-md bg-neutral-900 dark:bg-neutral-100 text-white dark:text-neutral-900 hover:opacity-90 transition-opacity font-medium"
>
Go back home
</Link>
</div>
</div>
);
}
3 changes: 2 additions & 1 deletion content/docs/meta.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,7 @@
"onchain",
"zkfetch",
"browser-extension",
"understanding-the-tech"
"understanding-the-tech",
"troubleshooting"
]
}
100 changes: 100 additions & 0 deletions content/docs/troubleshooting.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,100 @@
---
title: Troubleshooting
description: Common issues, log events, and debugging information for Reclaim Protocol integrations
---

## Log Event Types

When integrating with Reclaim Protocol SDKs, you may encounter various log events. Understanding these events helps with debugging and monitoring your integration.


### Verification Flow Events

| Event Type | Level | Description |
|------------|-------|-------------|
| `VERIFICATION_FLOW_STARTED` | INFO | The verification flow has been initiated by the user. |
| `IS_RECLAIM_VERIFIER` | INFO | Checking if the current environment is a Reclaim verifier. |
| `IS_RECLAIM_INAPPSDK` | INFO | Checking if the current environment is a Reclaim inapp SDK. |
| `RECLAIM_VERIFICATION_DISMISSED` | INFO | The Reclaim verification process was dismissed by the user. |
| `RECLAIM_VERIFICATION_SKIPPED` | INFO | The Reclaim verification process was skipped. |

### SDK Version Events

| Event Type | Level | Description |
|------------|-------|-------------|
| `UPDATE_AVAILABLE` | WARNING | An update for inapp SDK is available. Use is still allowed. |
| `SDK_OUTDATED` | ERROR | An update for inapp SDK is available and the current version cannot be used anymore. |
Comment on lines +25 to +26
Copy link

@coderabbitai coderabbitai bot Jan 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Minor copy edits for consistency.

Prefer “in-app SDK” and “URL” for standard casing.

✏️ Proposed doc copy fix 
-| `UPDATE_AVAILABLE` | WARNING | An update for inapp SDK is available. Use is still allowed. |
-| `SDK_OUTDATED` | ERROR | An update for inapp SDK is available and the current version cannot be used anymore. |
+| `UPDATE_AVAILABLE` | WARNING | An update for in-app SDK is available. Use is still allowed. |
+| `SDK_OUTDATED` | ERROR | An update for in-app SDK is available and the current version cannot be used anymore. |
@@
-| `LOADING_INITIAL_URL` | INFO | Sending request to load initial url. |
+| `LOADING_INITIAL_URL` | INFO | Sending request to load initial URL. |

Also applies to: 39-40

🤖 Prompt for AI Agents 
In `@content/docs/troubleshooting.mdx` around lines 25 - 26, Update the wording
for consistency: change occurrences of "inapp SDK" to "in‑app SDK" and ensure
"URL" uses uppercase. Specifically update the table rows containing
`UPDATE_AVAILABLE` and `SDK_OUTDATED` (and the similar occurrences around lines
39-40) to read "in‑app SDK" and "URL" where applicable so the casing is
consistent across the document.


### Session Events

| Event Type | Level | Description |
|------------|-------|-------------|
| `RECLAIM_INIT_SESSION_EXCEPTION` | ERROR | An exception when initializing a Reclaim session. |
| `RECLAIM_EXPIRED_SESSION_EXCEPTION` | ERROR | An exception for an expired Reclaim session. |

### Page Loading Events

| Event Type | Level | Description |
|------------|-------|-------------|
| `LOADING_INITIAL_URL` | INFO | Sending request to load initial url. |
| `WEB_PAGE_READY` | INFO | The first web page for verification is ready. |
| `PAGE_LOADING_STARTED` | INFO | Page loading started. |
| `PAGE_LOADING_STOPPED` | INFO | Page loading stopped. |

### Request & Matching Events

| Event Type | Level | Description |
|------------|-------|-------------|
| `REQUEST_INTERCEPTED` | INFO | A network request has been intercepted. |
| `REQUEST_MATCHED` | INFO | A network request has been matched against the provider's requirements. |
| `PROVIDER_SCRIPT_REQUESTED_CLAIM` | INFO | The provider script has requested a claim. |

### Claim Events

| Event Type | Level | Description |
|------------|-------|-------------|
| `PREPARING_CLAIM` | INFO | The claim is being prepared. |
| `VALIDATING_CLAIM_PARAMETERS` | INFO | The claim parameters are being validated. |
| `STARTING_CLAIM_CREATION` | INFO | The process of creating a claim is starting. |
| `CLAIM_CREATION_STARTED` | INFO | The claim creation process has officially started. |

### Validation Errors

| Event Type | Level | Description |
|------------|-------|-------------|
| `X_PATH_MATCH_REQUIREMENT_FAILED` | ERROR | An XPath match requirement for claim validation has failed. |
| `JSON_PATH_MATCH_REQUIREMENT_FAILED` | ERROR | A JSONPath match requirement for claim validation has failed. |
| `REGEX_MATCH_REQUIREMENT_FAILED` | ERROR | A regex match requirement for claim validation has failed. |
| `NO_PARAMETERS_FOUND` | ERROR | No parameters found. |
| `CLAIM_PARAMETER_VALIDATION_FAILED_EXCEPTION` | ERROR | An exception for failed claim parameter validation. |
| `NO_RESPONSE_MATCH_WARNING` | WARNING | A warning that no response matched the provider's requirements. |

### Proof Events

| Event Type | Level | Description |
|------------|-------|-------------|
| `PROOF_GENERATED` | INFO | A proof has been successfully generated. |
| `SUBMITTING_PROOF` | INFO | The generated proof is being submitted. |
| `PROOF_SUBMITTED` | INFO | The proof has been successfully submitted. |
| `PROOF_GENERATION_FAILED_EXCEPTION` | ERROR | An exception for a failed proof generation. |
| `PROOF_SUBMISSION_FAILED` | ERROR | The proof submission has failed. |

### Exception Events

| Event Type | Level | Description |
|------------|-------|-------------|
| `RECLAIM_VERIFICATION_PLATFORM_NOT_SUPPORTED_EXCEPTION` | ERROR | An exception indicating that the platform is not supported for Reclaim verification. For example, a 32-bit Android device. |
| `INVALID_REQUEST_RECLAIM_EXCEPTION` | ERROR | An exception for an invalid Reclaim request. |
| `RECLAIM_VERIFICATION_CANCELLED_EXCEPTION` | WARNING | An exception indicating the verification process was cancelled for the user. |
| `RECLAIM_VERIFICATION_PROVIDER_LOAD_EXCEPTION` | ERROR | An exception during the loading of a verification provider. |
| `RECLAIM_ATTESTOR_AUTH_EXCEPTION` | ERROR | An exception related to attestor authentication. |
| `RECLAIM_VERIFICATION_NO_ACTIVITY_DETECTED_EXCEPTION` | ERROR | An exception when no user activity is detected during verification. |
| `ATTESTOR_NOT_RESPONDING` | WARNING | The attestor is not responding. |
| `CLAIM_CREATION_CANCELLED_EXCEPTION` | ERROR | An exception indicating the claim creation was cancelled. |
| `CLAIM_CREATION_TIMED_OUT_EXCEPTION` | ERROR | An exception indicating that the claim creation process has timed out. |

### Result Events

| Event Type | Level | Description |
|------------|-------|-------------|
| `RESULT_RECEIVED` | INFO | A result has been received. |
Binary file added public/favicon.ico
View file
Open in desktop
Binary file not shown.