Skip to main content
Before contacting support, record:
  • the Niblet CLI version;
  • operating system and CPU architecture;
  • the exact command that failed;
  • the error message with tokens and personal data removed;
  • the app ID or display name, not device credentials;
  • whether the issue reproduces in a fresh local preview; and
  • whether physical hardware, browser simulation, or both are affected.
For product support, use the support entry in the Niblet dashboard. For runtime or documentation bugs, open an issue in the relevant Niblet repository when it is public and the report contains no private data.
Never send Wi-Fi passwords, OAuth codes, access tokens, refresh tokens, API keys, device feed URLs, signing material, full customer records, or unredacted support bundles.

​
Security reports

Do not open a public issue for a vulnerability. Use the private security contact published by Niblet once the disclosure program is active.