Managani Docs

Appearance

Desktop Troubleshooting ​

Browser Sign-In Succeeds but Desktop Does Not Connect ​

  • Return to Managani promptly after browser authorization. The sign-in session expires after five minutes.
  • Confirm Desktop and the browser used the same server.
  • For an authorized private v1 test server, confirm it exposes /oauth/desktop-config and supports the built-in Desktop client.
  • Use HTTPS for private v1 test servers.
  • Start sign-in again to create a fresh PKCE session.
  • Select Reset saved sign-in data if the stored server or session is wrong.

Notifications Do Not Appear ​

  1. Allow Managani notifications in operating-system settings.
  2. Open Settings > Notifications in Desktop.
  3. Enable native notifications and the required source.
  4. Confirm Managani is still running and Do Not Disturb is not active.

Managani does not show a duplicate notification for a chat already open in the focused window.

Counts Look Stale ​

Show the Managani window and confirm it can reach the configured server. Counts refresh after realtime events and periodic account bootstrap refreshes. Fully quit and reopen Desktop if a reconnect does not restore them.

A Global Shortcut Does Not Work ​

Another application or the operating system may own the same chord. Open Settings > Notifications > Desktop notifications, record a different shortcut, and save it. Managani restores the previous working set when registration fails.

Confirm Managani Desktop is installed and has been launched at least once. Only com.managani.desktop://open and the reserved authentication callback are supported. See Desktop Links.

Update Checks Fail ​

  • Confirm https://transfer.managani.com/apps is reachable.
  • Check VPN, proxy, firewall, or content-filter settings.
  • Retry from Check for updates in the application or tray menu.
  • Download the current package from the Desktop page when necessary.

For Managani Cloud, see Support. For an authorized private v1 test server, confirm the public application origin and OAuth endpoints are reachable. Supported public self-hosting is planned for v1.