cometchat-ios-troubleshooting — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited cometchat-ios-troubleshooting (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Ground truth:CometChatUIKitSwift5.1.22 +CometChatSDK4.1.7 (symbols verified vscatalogs/ios-v5.json); signatures FETCHED viacometchat-ios-core/references/docs-map.md; the invariants below (init→login order, credentials flow, SPM-only) areRULES.md+cometchat-ios-core. This diagnostics catalog is cross-checked against the live{DOCS_BASE}/ui-kit/ios/troubleshooting.mdpage (base + paths incometchat-ios-core/references/docs-map.md), and adds the host-side/runtime symptoms it doesn't cover.
cometchat-ios-core — the correct init→login→render order, the Secrets.xcconfig→Info.plist→Bundle.main credential flow, and the SwiftUI launch hook the fixes below restore.An iOS CometChat integration compiles but misbehaves at runtime: a screen that never fills, login that does nothing, or empty data.
The two dominant causes of "the screen never populates":
cometchat-ios-core).Secrets.xcconfig → attach-to-configs → declare-in-Info.plist → read-via-Bundle.main chain has four steps; miss one and you init with the literal placeholder, which then fails auth.| Symptom | Likely cause | Fix |
|---|---|---|
| Screen never populates, no error | login before init resolved | Chain them: call login only inside the init completion (cometchat-ios-core references/swiftui.md) |
| Auth fails immediately | Wrong Region, or creds read as $(...) | Region must match the dashboard app; verify Bundle.main returns the value, not the literal $( |
Values are the literal $(...) | xcconfig not attached, or Info.plist key missing | Attach Secrets.xcconfig to the build configs AND declare each key in Info.plist (references/setup-credentials.md §2-§3) |
| SPM won't resolve / kit crashes at runtime | CometChatSDK version drifted from the kit's exact pin | Pin CometChatUIKitSwift 5.1.22 + CometChatSDK 4.1.7 + CometChatCallsSDK 5.0.3 exactly (cometchat-ios-core Install) |
| Build fails after adding a Podfile | Tried CocoaPods | SPM only — a Podfile is a detection signal, not an instruction; remove the pod integration |
| Conversations empty | New app has no conversations, or wrong scope | Send a first message; check the request scope |
login "user not found" | UID does not exist in the app | Use a real UID (Dashboard → Users; fresh apps seed cometchat-uid-1) — never a guessed superhero* |
| Calls fail / no permission prompt | Missing usage-description strings or VoIP entitlement | Add NSCameraUsageDescription + NSMicrophoneUsageDescription; enable the VoIP entitlement (cometchat-ios-push/-calls) |
| Works in dev, fails in release | Auth Key stripped for release but still using login(uid:) | Switch to login(authToken:) with a server token (cometchat-ios-production) |
Enable SDK logging and read the Xcode console: an init/lifecycle error (a call made before init() resolved) is the usual "nothing renders" cause; auth errors are almost always Region or a literal-placeholder credential. Then fetch the feature's page via cometchat-ios-core/references/docs-map.md. Never diagnose from the binary framework's headers or from memory — fetch the documented signature.
init and login both resolve (in order) before the chat screen renders · Bundle.main returns real credential values, not $(...) · the exact kit/SDK versions are pinned · conversations render or show the empty state · a message sends and arrives · calls prompt for permission.
Do not hard-code credentials to get past the $(...) literal — fix the xcconfig/Info.plist chain; do not add CocoaPods to work around an SPM resolve issue — pin the exact versions; do not hard-code a UID to dodge "user not found."
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.