cometchat-troubleshooting

A blank CometChat chat screen often stems from missing environment variables, CSS import issues, or incorrect init and login ordering. Run `cometchat doctor` verify checks to pinpoint the exact failure and apply targeted file-level fixes.

Fix CometChat 401 Unauthorized errors by verifying local integration state and environment correctness. Use `cometchat doctor` to read verify outputs and confirm API keys and region settings are properly loaded before login.

CometChat UI kit CSS variables fail to load when there are CSS import issues or drifted file structures. Diagnose this by running verify checks to inspect the integration state and reviewing modified owned files.

Troubleshoot missing CometChat messages by checking init and login ordering problems alongside environment correctness. Use the cometchat-docs MCP for symptom-to-cause lookups when verify results do not fully explain the issue.

Detect CometChat configuration drift by running `cometchat doctor` to identify modified or missing owned integration files. It guides you on whether changes were intentional before recommending a restore and post-fix verify loop.

Yes, you can diagnose local CometChat integration failures by verifying code structure, environment variables, and file drift offline. However, resolving dashboard or network causes and using the cometchat-docs MCP lookup requires connectivity.