Product Updates
New product updates and improvements
Bug Grouping: Network Logs and User Steps
What's new?
Bug Grouping can now use two additional signals beyond report descriptions:
Network Logs: the failing endpoints and HTTP errors hit during the user's session.
User Steps: the screens the user moved through, the screen they were on when the bug was reported, and the last action they took.
Reports that hit the same failing endpoint or land on the same error screen now group together, even when their titles and descriptions don't match.
Reports that read alike but exercise different parts of the app stay in separate groups.
Why this matters?
Reports with empty, vague, or short descriptions can now be grouped reliably.
Strengthens the grouping logic and further reduces manual triage by tightening what each group actually represents.
Availability
Available now on top of Bug Grouping, off by default.
No SDK update required.
Applies to new reports received after the setting is turned on. Not retroactive.
Note
Interested in trying this out? Please reach out to our support team or your Customer Success Manager to enable it for you. You can enable Network Logs only, User Steps only, or both.
Update Bugs from the Luciq MCP Server
What's new?
The new
update_bugtool lets agents close, reopen, reprioritize, retag, and mark bugs as duplicates, directly from the IDE.This is the first write tool in the Luciq MCP Server. Until now, agents could only read; any state change meant switching to the dashboard.
Available now in the Luciq MCP Server alongside the existing read tools.
Why this matters?
Bug triage now runs end-to-end inside the IDE. Agents can investigate a bug, decide what to do, and apply the change without ever leaving the editor, removing the context switch that previously broke agentic workflows.
Feature Flag Filtering for list_crashes in MCP
What's new?
The
list_crashesMCP tool now accepts afeature_flagsfilter.You can filter by a bare flag name when no variant was set (e.g.,
private_mode).You can also filter by the combination of flag name and variant when one is set (e.g.,
checkout_flow -> external_request).
Why this matters?
Crash investigation through the MCP can now be scoped to releases gated by specific feature flags, making it faster to isolate the impact of an experiment or rollout from inside the IDE.
Crashes Filter in Session Replay
What's new?
You can now filter Session Replay sessions by a specific crash type.
Why this matters?
When chasing a specific crash class such as OOMs or ANRs, you land directly on the replays where those happened instead of digging through every crashing session. This continues a recent run of filtering improvements across Flows, Feature Flags, and Multi-value User Attributes.
Detect Agent: App Context Awareness
What's new?
Every Detect Agent analysis is now enriched with the customer's actual app name and description pulled from the App Store and Play Store.
The enrichment activates for apps that have
bundle_idconfigured in the SDK.
Why this matters?
The agent stops running a generic prompt against a banking app, a kids' game, and an expense tracker as if they were the same product. Detection precision and recall climb double digits on both Visual Issues and Broken Functionality categories when app context is available.
Multi-value Filtering for User Attributes in Crash Reporting
What's new?
You can now filter Crash Reporting by multiple user attribute values at once.
All available values for each user attribute surface directly in the filter, so you no longer have to enter them manually.
Select multiple values (e.g., USWest1, USWest2, USEast1) in a single filter and see all matching crash occurrences in a unified view.
Why this matters?
Investigating crashes across multiple user attribute values no longer requires filtering one value at a time, gathering insights separately, and piecing them together across pages. You see the full picture in a single view, with less manual work.
Detect Agent: Dynamic Screenshot Range per Issue
What's new?
Detect Agent now surfaces the full span of screenshots affected by each issue, not just a single anchor frame.
The range adapts per occurrence and can be a single screenshot or several, depending on how the issue plays out across the session.
Why this matters?
Reviewers see the issue with the same continuity the user experienced, instead of guessing what came before and after a single anchor frame.
All APM Metrics Available via MCP
What's new?
The three MCP tools introduced for Network (List APM Groups, List Network Group, List Network Occurrence) now accept any APM metric as a parameter.
You can pull data for App Launch, UI Hangs, Screen Loading, Flows, and the rest of the APM metric set in addition to Network.
Natural-language queries like "list my worst app launches" now resolve directly to the right tool call with the App Launch metric.
Why this matters?
Performance investigation across the full APM surface is now accessible from your IDE, not just network data. Slow launches, hangs, screen-load problems, and flow regressions can be inspected in the same agent workflow.
Crash Aggregations for AI Agents: No-LLM Mode
What's new?
Crash Aggregations can now run in a mode that uses only Luciq's data, with no LLM call involved.
This complements the existing AI-powered mode introduced earlier in May.
Why this matters?
Customers with constraints around AI features or external LLM calls can adopt Crash Aggregations without running into policy blockers, while still getting the structured, agent-ready crash data the feature was built to surface.
User Event Parameters
What's new?
You can now attach key-value parameters to any user event you log. For the event
login_prompt, you can include parameters liketrigger: onboardingandstatus: success.Parameters surface inline when expanding the user event in the logs.
Supported across iOS, Android, and live on the dashboard.
Why this matters?
User event parameters move debugging from "what happened" to "why it happened" without needing to search for extra clues. You get richer, more contextual information directly in your event logs, making it faster to understand user behavior and diagnose issues.
Network Support in MCP
What's new?
You can now query network data directly through the Luciq MCP Server with the same filtering and sorting available on the dashboard.
List APM Groups: Surface your worst-performing endpoints ranked by Apdex or failure rate.
List Network Group: Pull everything on a specific network group, including charts, spans, dimensions, failures, and outliers.
List Network Occurrence: Drill into specific or sample occurrences for deeper debugging.
Why this matters?
Network performance data is now accessible directly from your IDE alongside crash and bug data. You can investigate slow endpoints, high failure rates, and individual network occurrences without leaving your coding environment.
Per-Variant appToken Support for Android
What's new?
You can now configure different Luciq app tokens for different Android build variants directly in the Gradle plugin using the
variantConfigurationsblock.This lets you route mapping file uploads to separate Luciq dashboards (e.g., Production vs QA) per variant.
Why this matters?
Previously,
appTokenwas a single global field shared across all variants. Teams with separate QA and Production environments had to manually upload mapping files for non-production variants. This release closes that gap.
Availability
Available in SDK v19.7.0.
Screen Loading for React Native
What's new?
You can now measure how long each screen takes to become interactive (TTID) and fully loaded (TTFL) directly from the React Native SDK.
An automatic approach tracks screen loading out of the box.
A manual approach is available for customization when you need to define the screen loading boundaries yourself.
Why this matters?
Screen loading measurement has been one of the most requested features from React Native users. Instead of relying on workarounds, you now have built-in, out-of-the-box support for understanding your app's screen loading performance.
New Jira Authentication Methods
What's new?
Jira OAuth 2.0: You can now set up Jira authentication with a single click using OAuth.
Jira Service Accounts: Support for special accounts that are not tied to individual users, with Scoped API Tokens and OAuth credentials. These continue working even as team members change.
Why this matters?
Atlassian has introduced changes to API tokens with a maximum expiry of 1 year, requiring annual rotation. The new OAuth and Service Account options provide more convenient and resilient authentication methods that reduce maintenance overhead and avoid disruptions from token expiration or employee turnover.
Availability
Both authentication methods are live now. Documentation has been updated.
DAU Usage Page
What's new?
A new DAU Usage page is now available on the dashboard, giving you direct visibility into your Daily Active User consumption.
View your average usage over the last 6 months.
See over-time usage trends for the last 6 months.
Get a usage breakdown by individual apps.
Why this matters?
You no longer need to rely on your account team to know your DAU usage. The new self-serve page lets you monitor your consumption directly, making it easy to track trends and plan ahead.
Feature Flag Filter in Session Replay
What's new?
You can now filter sessions by feature flags or experiments in Session Replay to scope replays to sessions where specific flags were active.
Why this matters?
This helps you cut through the noise and surface the most relevant sessions when investigating issues related to specific feature flags or A/B experiments, so you always know where to look when it counts.
Crash Aggregations for AI Agents
What's new?
Luciq now processes crash occurrences and distills them into structured, AI-ready aggregations that AI agents can consume without hitting context window limits.
Full crash content is available directly in the IDE, eliminating the need to context-switch to the dashboard.
Agent mode in the AI Debugging Assistant lets you view aggregations, copy or download them as a Markdown file, ready to feed into any AI agent or workflow.
Why this matters?
Hard crashes generate thousands of occurrences, and reviewing them one by one is impractical. Feeding raw crash data into an AI agent burns tokens and hits context limits fast. Crash Aggregations bridge that gap by delivering structured, consumable data that powers the AI debugging workflows you actually want to use.
Availability
Available now on the dashboard. MCP tools for pulling aggregations directly into your coding agent and IDE are coming soon.
Detect Agent: Grouping Experience Redesign
What's new?
Cleaner cards with Single vs. Group pills, issue counts, and first/last seen timestamps.
Sortable lists by recency or frequency (occurrences and first/last seen).
Editable bug reports: you can now report and edit bugs directly from Broken Functionality issues.
Refined issue details with a cleaner detail drawer and screenshot carousel.
Structured feedback: thumbs-down responses now include structured reasons, and ungrouping prompts ask for context to help refine detection.
Why this matters?
The redesigned grouping experience makes it easier to triage and act on issues detected by the Detect Agent. Better sorting, cleaner cards, and the ability to report bugs directly from issues streamline your workflow.
Smarter Crash Grouping for iOS
What's new?
Improved crash grouping logic for iOS when the top app frame in a stack trace is compiler-generated.
The system now walks down the stack to find the first meaningful frame (one with a valid file name and file path) and uses that for grouping and ownership assignment.
This change affects grouping for new crashes and ownership only.
Why this matters?
Previously, when the first app frame was compiler-generated, crashes could be grouped inaccurately and team ownership could be misattributed. This improvement ensures crashes are grouped by their actual root cause.
Surveys List: Filters, Pagination, and Faster Loads
What's new?
The Surveys list now supports filters by survey type and status.
Bookmarkable URLs allow you to save and share filtered views.
Pagination has been added for easier navigation.
Page load times have been significantly improved, especially for apps with a large number of surveys.
Why this matters?
Managing surveys is now faster and more efficient. Filters, pagination, and bookmarkable URLs make it easy to find exactly what you need without scrolling through long lists.
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.
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.
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.
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.
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.
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.
Automated NDK Symbol Upload via Gradle Plugin
What's new?
A single flag in your
build.gradlefile now handles everything for NDK symbol uploads: finding unstripped.sofiles, 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
.sosymbol 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.
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.
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.
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.
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.
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.
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.
Rage Taps Detection
What's new?
Rage Taps detection is now available across Session Replay, Crash Reporting, and Bug Reporting.
When a user taps the same area at least 3 times with no more than 300ms between consecutive taps, the taps are collapsed into a single Rage Tap event with a count showing how many taps occurred.
You can filter by Rage Taps to quickly find frustration moments across logs.
Why this matters?
Rage taps are a strong signal that something in the UI is not responding as expected. This feature helps you quickly identify and prioritize UX issues that frustrate your users the most.
KMP SDK Now in Beta
What's new?
The Luciq KMP (Kotlin Multiplatform) SDK is now available in beta, providing a single integration point in commonMain for full observability across both iOS and Android.
Supported features include Crash Reporting, Bug Reporting, Session Replay, APM, In-App Surveys, In-App Replies, Feature Requests, and Network Logging (with a Ktor plugin).
Why this matters?
If you use Kotlin Multiplatform, you can now instrument your app from a single shared module instead of maintaining separate integrations for each platform. This is the first KMP SDK to offer the full suite of crash reporting, session replay, and bug reporting in one package.
Availability
Beta SDK is available in production now. Full documentation is available at docs.luciq.ai/kmp.
AI Common Reproduction Steps
What's new?
A new "Generate steps" action is available inside the AI Crash Insights drawer for any crash.
Clicking it uses AI to analyze crash occurrences and generate clear, structured steps to reproduce the crash.
Why this matters?
Reproducing crashes, especially ANRs, OOMs, and edge-case crashes, is one of the most time-consuming parts of mobile debugging. This feature automates that process, giving your developers actionable reproduction steps without manually combing through thousands of occurrences.
Line Number Exclusion from iOS Crash Grouping
What's new?
iOS crashes sharing the same root cause but differing only in line numbers (e.g., after a code refactor or minor code shift) are now grouped together.
Line numbers are excluded from the grouping logic, so related crashes are no longer split into separate groups.
This applies only to new incoming crash occurrences. Historical crash groups remain unchanged.
Why this matters?
Code refactors and minor code changes previously caused identical crashes to be split into separate groups, making it harder to assess true crash impact. This improvement ensures cleaner, more accurate crash grouping.
Device Performance Class Visibility and Expandable Replay Panel
What's new?
Bug details, crash occurrences, and session replays now display a device performance class badge (low-end, mid-range, or high-end) for Android devices.
When data collection is reduced on lower-end devices, empty states now explain why data is limited instead of leaving you guessing, with links to documentation for further details.
The screenshot panel in Session Replay is now expandable, so you can resize it for a better viewing experience without needing to open the lightbox.
Why this matters?
The device class badge and descriptive empty states remove confusion when encountering missing screenshots or incomplete session data on constrained devices. The expandable replay panel makes it significantly easier to follow session replays alongside logs.
Surveys: Auto-Pause After Reaching Response Limit
What's new?
You can now set a maximum response limit for any survey. When the limit is reached, the survey is automatically paused.
The paused survey can be republished at any time with a new limit, without re-targeting users who already responded.
The response limit counts completed (submitted) responses only, not impressions or views.
Why this matters?
This eliminates the need to manually monitor and pause surveys, enabling controlled data-collection campaigns with a defined response cap.
Availability
Available for NPS, Custom, and App Rating surveys using Auto targeting.
Custom Spans for APM
What's new?
You can now define custom spans using a start and end API to measure the duration of any operation in your app.
A completed span API is also available for operations that started before SDK initialization.
Custom spans appear in the spans table on the dashboard and can be filtered alongside other span types.
Each custom span is automatically attached to the running metric (App Launch, Network, Flows, etc.) based on its timestamp.
Why this matters?
Custom spans give you full flexibility to measure and monitor the performance of any operation specific to your app, providing deeper insight beyond the default metrics.
Availability
iOS: SDK v19.5.0+. Android: SDK v19.3.0+. React Native and Flutter: Coming soon.
Time Zone Support in Crash Charts
What's new?
Crash charts across the Crashes list, Crash details, and App Health pages now correctly reflect your selected time zone.
Data aggregation and bucketing are now performed in your chosen time zone, eliminating issues with missing buckets, shifted data, and incorrect day boundaries.
Why this matters?
Previously, chart data could appear misaligned for users in time zones behind UTC, leading to confusion when comparing data across tools. This fix ensures accurate, trustworthy, and consistent chart data regardless of your location.
Metadata and Filtering in Surveys
What's new?
Survey responses now include metadata such as User ID, Country, App Version, Device, and OS.
Each response carries its own environment context, similar to Bug Reports, Crash Reports, and Session Replays.
You can filter responses by any of these metadata fields directly on the dashboard.
Why this matters?
Product and customer experience teams can now analyze sentiment by app version, country, device, and more. This makes it easier to detect release-specific issues or region-specific trends, and enables deeper analysis when exporting responses.
Availability
Supported across all survey types (NPS, Customer Survey, App Rating). Available to all customers.
Bug Grouping: Alerts and Rules
What's new?
If you have Bug Grouping enabled, you can now configure alerts and rules based on report type.
Alerts can target all reports (masters, ungrouped, and duplicates) or only master and ungrouped reports to reduce noise.
Automatic tags are added to reports: "Luciq_Master_report" when a report becomes a master, and "Luciq_Duplicate_report" when marked as a duplicate. These tags can trigger rules or workflows.
The Triage Agent automatically adds a comment when a new duplicate is added to a master report.
Why this matters?
You can avoid being overwhelmed by duplicate-triggered alerts and build smarter automation workflows based on report grouping type. Tag-based rules also improve visibility in integrations like Jira through tag and comment sync.
Availability
Available for all customers with Bug Grouping enabled.
Session Insights [Detect Agent] is now available in Session Replay
What’s new?
Session Insights is now available in production
It provides you with the insights of a specific session
Why this matters?
Understanding session context typically requires digging through timelines, screenshots, and logs, which can be time-consuming for customers.
Session Insights summarizes the user’s actions and experience in a few seconds, helping teams understand what happened in a session much faster.
Availability:
Available now and released to all Self-serve customers
Available for Enterprise customers upon request
Video-Like Replay in Session Replay
What's new?
Session Replay now supports video-like playback by capturing screenshots at higher frequency, creating a smoother replay experience.
You can control when screenshots are captured: on navigation, on navigation and interaction, or at a set frequency.
You can also adjust screenshot quality (High, Normal, or Black & White) to balance detail with storage.
A size limit of 1 MB worth of screenshots per session applies. Lowering screenshot quality allows more screenshots to be captured within that budget.
Why this matters?
Reviewing session replays now feels more like watching a video, making it easier to follow user flows and identify issues without gaps in the visual timeline.
Availability
Android SDK v19.1.0+ and iOS SDK v19.2.0+.
WebViews Support for iOS and Android
What's new?
User Steps and Repro Steps now capture interactions inside WebViews for Bug Reports, Crash Reports, and Session Replay.
Network requests happening within WebViews are now tracked in Network Logs.
Screenshots now include WebView content in all reports.
Why this matters?
Many apps rely on WebViews for critical flows like login, checkout, or account setup. Previously, these were blind spots in debugging. With this update, you get full visibility into what happens inside WebViews, just like native screens.
Availability
iOS and Android SDK v19.2.0+. Both platforms require opt-in via SDK APIs. WebView masking is enabled by default for privacy.
Bug Grouping [Beta]
What’s new?
Bug Grouping is now released in Beta
The feature automatically groups duplicate bugs using AI.
Why this matters?
It removes the high, unnecessary friction developers face when manually marking duplicate bugs.
Free-Typing User Events in Survey Targeting
What's new?
When configuring survey targeting, you can now free-type exact user event names if the event you need is not visible in the dropdown.
This works across all survey types that support event-based targeting.
Why this matters?
If your app has a large number of user events (beyond the 400 shown in the dropdown) or uses SDK-defined events that were not previously surfacing, you can now target any of them by simply typing the event name.
AI-Detected Issues: New Dedicated Page
What's new?
A new dedicated page for AI-detected issues is now available, letting you browse "Visual Issues" and "Broken Functionality" in separate, organized lists.
Each issue includes a description, screenshots, and a quick action to report it as a bug directly from the page.
A new entry point from the Session Replay list gives you quick access to all AI-detected issues across your sessions.
Why this matters?
You no longer need to open each session individually to find AI-detected issues. This page gives you a consolidated view of all detected issues across sessions, saving significant time during triage.
Export CSV for App Ratings
What's new?
You can now export App Ratings survey results as a CSV file, with results delivered directly to your email.
This follows the same export behavior already available for NPS and Custom Surveys.
Why this matters?
Easily export and analyze your App Ratings data outside the dashboard without needing to request manual data exports.
Availability
Available under In-App Surveys > App Ratings Survey Results > Export CSV.
MCP Server: 10 Tools Organized by Debugging Workflows
What's new?
The MCP Server now includes 10 tools, organized around the real questions you ask while debugging:
App context: quickly understand which app you are working with.
Crash analysis: access crash groups, detailed crash data, and pattern insights.
Occurrence-level context: view device info, OS, logs, and user details for any occurrence.
App hang visibility: identify and investigate app hangs across platforms.
Bug and review correlation: connect SDK-reported bugs and store reviews back to stability data.
Why this matters?
Instead of navigating a flat list of API tools, you can find exactly what you need based on the debugging question you are trying to answer, making the MCP Server more intuitive and productive.
AI-Powered PR Review
What's new?
A new AI-powered PR Review feature is now available. Once enabled, you can mention Luciq in any GitHub pull request to get an automated review.
Luciq analyzes the PR, detects potential bugs or issues, and recommends fixes directly in the PR comments.
To use it, connect your code repository under Settings > Source Code Management and enable PR Review.
Why this matters?
Catch bugs and issues earlier in the development cycle. AI-powered reviews help your team ship more stable code by surfacing problems before they reach production.
OAuth for MCP Server
What's new?
OAuth authentication is now available for the MCP Server, replacing the need for manual token generation.
Authenticate directly through the Dashboard under Luciq MCP > Connect.
For existing MCP users, previously generated tokens continue to work. You can optionally switch to OAuth by reconnecting.
New users can get started with OAuth right out of the box.
Why this matters?
Getting started with the MCP Server is now easier and more secure. OAuth removes the extra step of generating and managing tokens, so you can connect your IDE to Luciq faster.
GitHub Integration for Dynamic Team Ownership
What's new?
You can now integrate with GitHub via Source Code Management to fetch your CODEOWNERS file and automatically assign crash ownership to the right teams.
The integration can be used for both the Resolve Agent and CODEOWNERS-based team ownership, or just one of the two.
Why this matters?
Crash ownership is automatically kept in sync with your existing CODEOWNERS file, so the right team is notified without any manual configuration on the Luciq side.
Report Bugs from AI-Detected Issues
What's new?
If you have AI-detected issues enabled (Visual Issues and Broken Functionality), you can now report a bug directly from any AI-detected issue.
Bugs reported this way are automatically labeled as AI issues in the bug reporting list for easy identification.
Why this matters?
Streamlines the workflow from AI-detected issue to actionable bug report, so your team can triage and fix problems faster without switching between different tools or manually re-entering information.
One Code Apps Support for Surveys, Issues, and Session Replay
What's new?
If you use a shared codebase across multiple apps (one code apps), you can now:
Target surveys to a specific app using bundle ID.
Filter the issues list by bundle ID.
Filter Session Replay recordings by bundle ID.
Why this matters?
Teams with shared codebases can now isolate data per app across surveys, issues, and session replays, making it easier to analyze and act on feedback and bugs for each app individually.
Self-Serve Token Generation for MCP Server
What's new?
You can now generate authentication tokens for the MCP Server directly from the dashboard, under Account Management > Luciq MCP.
The page provides the token and the JSON configuration script needed to connect to the MCP server.
Each token is per user and works across all AI clients (e.g., a single token works for both Claude and Cursor).
Why this matters?
No more waiting on support to get set up with the MCP Server. You can generate tokens and start using the integration on your own, right from the dashboard.
Luciq MCP Server Launch
What's new?
The Luciq MCP Server is now live. Tools like Cursor, Claude Code, and Copilot can connect directly to Luciq.
Developers can pull crash data, triage issues, and debug right from their IDE without switching to the dashboard.
Ask questions about crashes, crash details, and patterns and start debugging right away in the IDE.
Why this matters?
No more copying stack traces from the dashboard and pasting them into your IDE or AI assistant. Luciq now has a seat inside your development environment, making debugging faster and more seamless.
New Predefined Roles and Seat Management
What's new?
Two new predefined roles are now available: Associate and Observer, giving you more granular control over team member permissions.
A redesigned seat management experience makes it easier to manage who has access and at what level.
Why this matters?
With more role options, you can tailor access levels to match how different team members actually use the platform, improving security and reducing noise for those who only need limited visibility.
Availability
Available for accounts on the enterprise (DAU-based) pricing plan.
APM Flows: Android Occurrences Connected to Session Replay
What's new?
Android APM Flow occurrences are now linked to Session Replay. You can click "View Session" on any occurrence to watch the full session that led to the issue.
This was already available for iOS and is now extended to Android. The connection works retroactively on older occurrences as well.
Why this matters?
You no longer need to guess what happened before a performance issue on Android. Session Replay gives you the full visual context alongside your APM data.
New Logs Experience in Session Replay
What's new?
Session Replay now features a redesigned logs experience with improved readability, navigation, and overall usability.
Logs within session recordings are easier to scan and follow, helping you trace user actions and events more efficiently.
Why this matters?
Debugging sessions becomes faster when you can clearly read and navigate through logs alongside the visual replay, reducing the time it takes to identify root causes.
Copy Alerts Between Apps
What's new?
You can now copy alerts from one app or environment to another, removing the need to manually recreate alert configurations.
Import your existing alert setups across apps and environments in just a few clicks.
Why this matters?
Managing alerts across multiple apps and environments is significantly faster, especially for teams with shared alert configurations across staging and production.
Hourly Timestamp Filtering & Flow Filter in Session Replay
What's new?
You can now filter sessions by a specific hour on a specific day using the enhanced date filter.
A new Flow filter lets you find all sessions where end users passed through a specific flow.
Why this matters?
Narrowing down sessions to a precise timestamp helps you quickly find the exact session you are looking for without scrolling through irrelevant data.
Last updated