Troubleshooting & Help Center

Troubleshooting & Help Center provides complete diagnostic guides, automated fix shortcuts, version synchronization steps, authentication recovery walkthroughs, and error solutions for SnippKit.

Whether you encounter stale app versions, password recovery issues, extension authorization errors, or site storage glitches, this guide covers step-by-step resolution workflows.

Overview

Browser caching, offline Service Workers, and local storage keep SnippKit fast and offline-ready. However, browser file caching can sometimes hold onto legacy assets after a new deployment.

SnippKit provides built-in automated troubleshooting tools (/settings/general), permission status monitors (/settings/device), and a dedicated Help Hub (/help).

Direct App Shortcuts

Visit the live Help Hub (/help), run automated cache cleanup at Settings → General (/settings/general), or inspect device permissions at Settings → Device (/settings/device).

Quick Diagnostic Index

Category	Issue / Symptom	Recommended Resolution
Version Sync	Seeing an old app version or UI layout break after an update.	Perform a Hard Refresh (`Ctrl + Shift + R` / `Cmd + Shift + R`) or run Automated Fix at /settings/general.
Authentication	Locked out, forgotten password, or OTP email issues.	Follow the 5-step password recovery guide at /help/signing-in or contact support.
Extensions	Chrome or VS Code extension returning 401 Unauthorized.	Generate a new API key at /settings/developer and re-authenticate your extension.
JaaS API	HTTP 401 response on private JSON endpoints.	Include `Authorization: Bearer sk_live_...` in your request headers.
SNiX CLI	Command line login failures or token mismatches.	Run `snix auth logout` and re-authenticate with your API Key (`sk_live_...`) via `snix auth login`.

1. Version Sync & Stability (`/help/refresh-app`)

If SnippKit is displaying an older version or unresponsive UI elements:

Step 1: Hard Refresh (Recommended)

Force your browser to bypass local caches and download fresh application assets:

Windows / Linux: Press Ctrl + Shift + R (or Ctrl + F5).
macOS: Press Cmd + Shift + R.
Incognito Mode: Open SnippKit in a Private/Incognito window to verify if browser extensions are causing conflicts.

Step 2: Automated Cache Cleanup (Easiest)

SnippKit includes one-click automated cleanup tools in your settings:

Navigate to Settings → General (/settings/general).
Click Clear Cache to delete cached web assets.
Click Reset Worker to unregister stale background Service Workers.
Click Wipe Site Data if persistent storage errors occur.

2. Authentication & Sign-In Recovery (`/help/signing-in`)

If you are unable to sign into your SnippKit account:

Password Reset Workflow

Navigate to the Sign In Page (/sign-in).
Enter your account email address and click Continue.
On the password prompt screen, click Forgot Password?.
Click Reset Password to request a One-Time Password (OTP).
Check your email inbox for the OTP code, enter it on screen, and set a new password.

Social OAuth Logins

If you originally signed up using GitHub or Google single sign-on (SSO) and lost access to your social account, reach out directly to support at /contact-us.

3. Device & Access Diagnostics (`/settings/device`)

To check whether your browser is granting required hardware or notification permissions:

Open Settings → Device (/settings/device).
Review live status rows for Camera, Microphone, Notifications, and Location.
Click the Refresh button to re-query active permission states.

Resetting Site Permissions

Desktop (Chrome / Edge / Firefox): Click the Lock Icon (🔒) in your URL address bar → Toggle site permissions → Refresh page.
Mobile (iOS Safari / Android Chrome): Tap the aA or Lock icon left of the URL bar → Select Site Settings → Adjust permissions.

4. Extension & Integration Troubleshooting

Chrome Extension

Symptom: Popup displays "Not Authenticated".
Fix: Open /extension-login in your browser while signed in, or reconnect from Settings → Extensions.

VSCode Extension

Symptom: Command Palette returns API error when saving code.
Fix: Open Command Palette (Ctrl+Shift+P / Cmd+Shift+P), run Snippkit: Set API Key, and paste a valid key (sk_live_...) generated at Developer Settings.

SNiX CLI

Symptom: snix run or snix snippets fails with unauthorized error.
Fix: Run snix auth logout to clear saved local credentials, then re-authenticate using snix auth login.

5. Contacting Support & Feedback

If an issue persists after trying the steps above:

Direct Support: Contact our team directly at /contact-us.
Feature Requests: Submit ideas or vote on the product roadmap at /feedback.

Profile Customization — Manage profile handle and security toggles.
SNiX CLI — Terminal CLI installation and command reference.
JaaS Service — Configure JSON as a Service REST endpoints.
VSCode Extension — Configure VS Code extension settings and API keys.