Logging & Diagnostics
Good diagnostic information shortens support time. Never include passwords, tokens, private keys, or sensitive clipboard content in logs, screenshots, or forum posts.
What to collect
| Category | Include |
|---|---|
| Platform | OS, OS version, device model, desktop/mobile platform |
| Octoclip | app version, install source, license state, sync mode |
| Reproduction | shortest steps that reproduce the issue |
| Layer | whether the clip was captured locally, transferred, and pasted/inserted |
| Network | same LAN or cross-network, VPN/proxy, guest Wi-Fi, firewall/router isolation |
| Content type | text, image, file, URL, SMS/OTP, rich text |
Minimal reproduction template
text
Platform A:Platform B:Octoclip versions:Sync mode: Nearby / Cloud / unclearLicense state: inactive / active / unclearTest content type:Steps:Expected:Actual:Does the source device record the clip locally? yes/noDoes the target device receive the clip? yes/noCan the target device paste/use the clip? yes/noDiagnostic order
- Capture: did the source device record the clip?
- Transfer: did the target device receive the clip?
- Paste/use: can the target insert or paste the clip into the destination app?
Do not debug all layers at once. Identify the failed layer first.
Was this page helpful?