Skip to content
- Go to Clients → Users and search for the user’s id (the one you pass to
Cimka.identify()).
- Open their latest session from Recent Sessions.
- Check the Problems tab for crashes, failed requests and error logs.
- Open the Timeline to see exactly what they did before the problem — screens, taps, requests and their responses.
- Click Generate Summary under AI Summary for a plain-language recap to paste into your ticket.
- If the problem depends on local state, open Local Storage while their session is live and Capture the app’s storage.
- You get a Crash Spike alert (bell icon, and by email for high priority).
- Open Log Components → Crashes and filter by the affected time range.
- Open the top crash. Check Stack Trace and the Device tab — is it one manufacturer or OS version?
- Use AI Analysis → Generate Analysis for a root cause and suggested fix.
- Check Statistics → Crash Stats → Crashes by Version to see whether a specific release introduced it.
- Open Statistics → Network Stats and look at Top Slow Endpoints and the status code distribution.
- Click the endpoint in Statistics → Endpoint Analyze to see its latency over time and By App Version.
- Expand recent requests in Request History to inspect headers and bodies.
- On Log Components → Network, run AI Analysis for flagged endpoints and recommendations.
- After rollout, open Analyze → Releases and compare the crash-free rate of the new version with the previous one.
- Watch Analyze → Alerts for New Fatal Issues and Regressions.
- Open Analyze → Dependencies, select the release and Run AI Security Scan to review new or updated libraries.
- Open Clients → Devices and check the Rooted, Simulators and Corrupted tabs.
- Use Analyze → Security Map to see where flagged devices are located.
- If needed, Block the device. The user sees a blocked screen with your contact details from Organization Info.
