> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/changelog/readme/2026-04.md). # April 2026 13 product updates shipped in April 2026. See [Product Updates](/changelog/readme.md) for the latest. {% updates format="full" %} {% update date="2026-04-30" %} ## Crash Insights: New Metrics and Visual Enhancements #### What's new? * The Crash Insights dashboard now includes percentage rates alongside absolute counts. * A crash-type breakdown (Fatal, OOM, ANR, Non-fatal) with affected users per type is now available. * A stacked bar chart showing daily crash distribution has been added. * You can now filter app performance data by date and app version. * The standalone Crash Insights page has been consolidated into the main view to eliminate data inconsistencies. #### Why this matters? * Raw crash counts alone can be misleading without rate normalization. With crash rates, type breakdowns, and everything in one consolidated view, you get the full stability picture at a glance. {% endupdate %} {% update date="2026-04-29" %} ## Device Class Filter in Bug Reporting #### What's new? * You can now filter bug reports by device class (low-end, mid-range, or high-end) in Bug Reporting. * The filter is available for all new bug reports received after this release. #### Why this matters? * Device class filtering helps you quickly isolate bugs that are specific to certain hardware tiers, making it easier to identify performance-related issues on lower-end devices. {% endupdate %} {% update date="2026-04-28" %} ## Flows Filter in Crash Reporting and Faster Session Replay Playback #### What's new? * Flows Filter in Crash Reporting: You can now filter crashes by Flow across the Crashes List, Crash Details, and Occurrences pages, making it faster to pinpoint stability issues tied to specific user journeys like checkout or onboarding. * Faster Session Replay Playback: Session recordings now include a playback speed control with 1x, 1.5x, and 2x options, letting you quickly scan through long sessions to find the relevant moment. #### Why this matters? * Understanding which user journeys are most impacted by crashes helps you prioritize fixes that protect critical business flows. And faster playback lets you reach the relevant moment of a bug or crash quickly without sitting through uneventful segments. {% endupdate %} {% update date="2026-04-20" %} ## Luciq MCP Server is Now Generally Available #### What's new? * The Luciq MCP Server is now available to every customer on every plan, with no feature flags or manual enablement required. * OAuth authentication with automatic client detection for one-click setup. * Self-serve token generation directly from the dashboard for programmatic and CI/CD use cases. * Multi-IDE support across AI coding tools. * 10 tools across 5 domains: Crashes, Occurrences, App Hangs, Bugs, and App Store Reviews. * A new MCP setup portal under Account Management with per-IDE integration guides, token management, and OAuth/Token tabs. #### Why this matters? * You can now query your crash data, bug reports, app hangs, and app store reviews directly from your IDE using natural language. Setup takes under 2 minutes, there is zero cost (included in all plans), and no source code access is required. #### Availability * Available on all plans for all customers. Head to Account Management in your dashboard to get started. {% endupdate %} {% update date="2026-04-20" %} ## Surveys: Conditional Branching Logic #### What's new? * You can now add branching and skip logic to Custom Surveys. * Supported on all three question types: single-select (branch based on the selected choice), stars (branch based on rating buckets), and text field (branch after answer submission). * Each choice can point to a specific target question or jump directly to the thank-you message to end the survey. * The Responses page only shows questions that were actually answered, with no placeholders for skipped ones. #### Why this matters? * Branching logic unlocks smarter, more personalized surveys by showing only relevant questions based on prior answers, helping you collect higher-quality feedback while keeping surveys shorter. #### Availability * Available on iOS SDK v19.6.0 and Android SDK v19.5.0. React Native and Flutter support coming soon. Applies to Custom Surveys only. {% endupdate %} {% update date="2026-04-19" %} ## Detect Agent: Continuous Monthly Monitoring #### What's new? * Detect Agent now distributes its monthly session analysis budget evenly across the entire month using a time-based quota system, instead of consuming sessions on a first-come-first-served basis. * The monthly quota is split into minute-level increments. Unused slots from quiet periods (nights, weekends) carry over to busier periods. * At month start, at least 1 session is analyzed immediately. By mid-month, roughly half the budget is used. By month end, the full allocation is consumed. #### Why this matters? * Previously, apps with high session volume could burn through the entire monthly analysis budget in the first few days, leaving no detection coverage for the rest of the month. Now, Detect Agent provides continuous monitoring across all 30 days. #### Availability * Live in production. No action needed on your part; the improvement is automatic. {% endupdate %} {% update date="2026-04-16" %} ## Automated NDK Symbol Upload via Gradle Plugin #### What's new? * A single flag in your `build.gradle` file now handles everything for NDK symbol uploads: finding unstripped `.so` files, packaging them by architecture, and uploading them automatically on every build. * Works with CMake and ndk-build. Supports all CPU architectures. * Per-variant Gradle tasks are hooked into the build lifecycle with clear success/failure logs for CI/CD pipelines. #### Why this matters? * Previously, uploading native `.so` symbol files for NDK crashes required building custom API upload scripts or manual uploads. This release gives you a plug-and-play Gradle solution that automates the entire process. #### Availability * Available in Luciq Android SDK. Documentation available in the deobfuscation setup guide. {% endupdate %} {% update date="2026-04-16" %} ## Resolve Agent: Real-Time Thinking Steps #### What's new? * When you trigger "Generate Fix" on a crash, the Resolve Agent now streams its real thinking process to the dashboard in real time as it works through your codebase. * You will see specific steps such as which files the agent is checking, what code paths it is analyzing, and what fix it is implementing. * Pipeline milestones (sandbox boot, finalization) always display, while file-by-file agent progress streams on top. * The experience works on both initial fix generation and feedback/retry flows. #### Why this matters? * When an AI agent takes 50+ seconds to generate a fix, seeing exactly what it is doing builds trust and transparency. Instead of watching a generic spinner, you now see the agent navigate your actual codebase step by step. #### Availability * Live in production for all Resolve Agent enabled accounts. {% endupdate %} {% update date="2026-04-14" %} ## AI Debugging Assistant Now Available on App Hangs and Force Restarts #### What's new? * The AI Debugging Assistant is now enabled on App Hangs and Force Restart pages, in addition to Crashes. * UI fixes based on earlier feedback have also been applied. #### Why this matters? * You can now use the same AI-powered root cause analysis, reproduction steps, and pattern insights to debug App Hangs and Force Restarts, not just crashes, giving you broader coverage across stability issues. {% endupdate %} {% update date="2026-04-14" %} ## Network Grouping Enhancements #### What's new? * High Cardinality Detection (automatic): Variable segments in network URLs are now automatically detected and replaced with wildcards. When a path segment has many unique values, it is automatically converted to a pattern and all matching occurrences are merged under one group. No action is needed on your part. * Double Asterisk Wildcards in Custom Groups: You can now use `**` as a multi-segment wildcard when creating custom network groups. A single `*` matches one path segment, while `**` matches any number of segments. #### Why this matters? * These enhancements significantly reduce noise in your network performance data by automatically cleaning up high-cardinality URL grouping, and give you more powerful tools to define custom grouping rules. {% endupdate %} {% update date="2026-04-12" %} ## Customize Network Failure Definitions #### What's new? * You can now exclude specific HTTP status codes (e.g., 404, 401) from failure and Apdex calculations for any network URL. * Navigate to the network details page, click "Customize failures" next to the Failures section, and add the status codes you want to exclude. * Changes apply to new occurrences going forward. #### Why this matters? * Some APIs intentionally return 4xx/5xx codes for non-error scenarios (for example, a 404 when no data is available). These were previously inflating failure rates and skewing Apdex scores. You now have full control over what counts as a failure. {% endupdate %} {% update date="2026-04-08" %} ## Symbolication and Mapping Files: Missing Visibility and Management #### What's new? * A new "Missing" tab is now available on every upload settings page (dSYMs, Mapping Files, NDK, Source Maps, Flutter Symbols), giving you a centralized view of all missing debug files sorted by app version and crash count. * Each missing file displays its identifier, app version, build number, and framework. * Bulk download and bulk delete actions are now supported on the Uploaded tab. * Real-time upload processing banners now track the status of your uploads from confirmation through processing to completion. * Pagination is now available across all upload settings tables. #### Why this matters? * Previously, discovering missing symbol files required opening individual crash reports one by one. Now, a single visit to Settings tells you exactly which files are missing, how many there are, and which ones to prioritize. {% endupdate %} {% update date="2026-04-06" %} ## AI Debugging Assistant for Crash Reporting #### What's new? * The AI Debugging Assistant is now available in Crash Reporting, bringing three powerful capabilities: * Root Cause Analysis provides plain-English explanations of why a crash happened, with direct links to the exact lines of code. * Automated Reproduction Steps reconstruct the full user journey leading to a crash, step by step. * Pattern Insights surface multi-factor correlations so you can tell whether a crash is a widespread problem or an edge case. * You can use these capabilities in any order. #### Why this matters? * Debugging crashes no longer requires hours of sifting through logs, guessing at reproduction steps, or manually determining the scope of an issue. The AI Debugging Assistant gives you the "why," the "how to reproduce," and the "who's affected" in one place. #### Availability * Available now on all accounts with AI Crash Insights enabled. Requires a minimum of 100 occurrences per crash group. {% endupdate %} {% endupdates %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.luciq.ai/changelog/readme/2026-04.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.