Instabug Unsupported SDK Data Collection Cutoff — when and how should I migrate?

Assess whether old Instabug SDK versions are causing silent data loss, since unsupported app versions stopped sending sessions and events after the June 30, 2025 support cutoff.

Upgrade every still-active app version to a supported Instabug/Luciq baseline if unsupported builds still have meaningful usage; migrate to Luciq only when you're already touching the SDK.

Blockers

Who this is for

Candidates

Upgrade every still-active app version to a supported Instabug/Luciq SDK baseline

As of 2026-03-29, the June 30, 2025 cutoff has already occurred. Luciq's official SDK support policy says versions below iOS 12.0.0, Android 11.5.2, Flutter 12.0.0, and React Native 12.6.1 are unsupported, and Luciq no longer processes sessions or events from app versions using those SDKs. That means crashes, bugs, and performance metrics from those app versions no longer appear in the dashboard, and those app versions also disappear from dashboard filters. Public pricing was not verified in the official docs reviewed; check official billing docs.

When to choose

Use this when the main question is whether telemetry gaps are caused by old mobile builds still in the field. If a meaningful share of users remain on app versions shipping those unsupported SDKs, the decisive action is to ship upgrades and push user adoption, because vendor-side collection is already off for those versions.

Tradeoffs

Fastest path to restoring visibility for supported app versions without a full vendor rebrand migration. The downside is that users who never update remain permanently invisible in Instabug/Luciq telemetry.

Cautions

Do not assume missing data is sampling or dashboard lag. The policy explicitly stops new session and event processing for unsupported SDK app versions, while retaining only already-collected historical data within the retention period.

Sources

Use the forced touchpoint to migrate from legacy Instabug SDK naming to Luciq SDK

As of 2026-03-29, Luciq's migration hub says the legacy Instabug SDK no longer receives new features or product updates, and critical updates and hotfixes ended in January 2026. The official migration guides target Luciq SDK 18.0.0 and support projects already on Instabug 16.x.x and above, with vendor guidance to upgrade older Instabug versions first. Luciq describes this as a one-time breaking change that replaces package dependencies and renames API calls, and says its scripts automate roughly 90 percent of changes with an estimated 2-3 hour migration for a medium-complexity project. Public pricing was not verified in the official docs reviewed; check official billing docs.

When to choose

Use this when you are already touching the SDK because of the post-cutoff blind spot and you want the actively maintained path rather than just clearing the minimum support floor. It is the better choice if you need future features, want to avoid staying on rebranded legacy packages, or must standardize new installs on the maintained SDK line.

Tradeoffs

You get onto the vendor's active SDK line and future roadmap, but this is a breaking migration with dependency, symbol, and config-file changes across app code and CI/build scripts.

Cautions

If you are on Instabug earlier than 16.0.0, Luciq recommends upgrading Instabug first before running the migration. Enterprise or on-prem setups have extra config work, including renaming `Instabug.plist` to `LuciqConfig.plist` on iOS and updating related keys.

Sources

Facts updated: 2026-03-29
Published: 2026-04-03

Related questions

Try with your AI agent

$ npm install -g pocketlantern
$ pocketlantern init
# Restart Claude Code, Cursor, or your MCP client, then ask:
# "Instabug Unsupported SDK Data Collection Cutoff — when and how should I migrate?"
Missing something? Request coverage