Skip to main content

Why am I facing a runtime crash when using an older Luciq iOS SDK on iOS 26?

This article covers a runtime crash in older Luciq iOS SDKs on iOS 26 and the needed steps to avoid it and ensure app stability.

Aya avatar
Written by Aya
Updated this week

What's happening?

The root cause of this crash is a technical conflict between a method in older Luciq SDKs (Instabug SDK) and a new method with the same name that Apple has introduced in its UIKit framework for iOS 26. This conflict can cause the Objective-C runtime to unpredictably call our SDK's code instead of Apple's, leading to a fatal crash.

All iOS apps using an affected SDK version are at high risk of crashing for any end-user who upgrades their device to iOS 26.

Who is Impacted?

This issue affects any application that includes a Luciq SDK version prior to Instabug iOS v16.0.2. This includes:

  • Native iOS SDKs.

  • React Native & Flutter SDKs that bundle an affected native iOS SDK version.

ℹ️ Please note that this is a runtime issue related to the user's OS version, not the version of Xcode you use to build your app.

How to avoid this?

We strongly recommend that you upgrade your Luciq SDK before the release of iOS 26 to ensure uninterrupted stability for your users.

  • For Native iOS: The issue is fully resolved in our native iOS SDK (Instabug iOS v16.0.2) and later.

  • For Flutter and React Native: The issue is fully resolved in our SDK (Instabug v15.0.3) and later.

Alternatively, you're more than welcome to request a Hot fix.

If you are using an SDK version of Instabug 15.0.0 or later and cannot immediately upgrade to 16.0.2, please contact our Support team to request a custom Hotfix build.

You can do so by pressing the chat bubble at the bottom-right corner of your dashboard or the Luciq website, or by emailing support@luciq.ai

We will provide a special version based on your current SDK that resolves this specific crash.


How do I check my current SDK Version?

To determine if you are affected, you first need to identify which version of the Luciq SDK you are using.

For Native iOS:

  • Swift Package Manager: Check the version number declared for the Luciq package in your Package.swift file or your Xcode project's "Package Dependencies" section.

  • CocoaPods: Look for the Luciq/Instabug version number in your Podfile.lock file.

For React Native & Flutter:

  • First, check the version of the Luciq/Instabug wrapper package in your package.json (for React Native) or pubspec.yaml (for Flutter).


FAQs

  • If my app seems to work on the iOS 26 beta, am I safe?

No. The crash is non-deterministic and may only occur in certain app flows. Your app remains vulnerable, and the risk of crashes will increase significantly after the public release of iOS 26. A proactive upgrade is the only way to ensure stability.

  • Will I see this crash on my Luciq dashboard?

    Yes, if the crash is triggered and successfully sent by a user, it will appear as a regular crash report on your dashboard. However, you should not wait to see these reports before taking action.

  • Are my Android users affected?

    No, this issue is specific to the Objective-C runtime on iOS and does not affect Android.

  • Are there other breaking changes in version 16.0.2?

    No, this version mainly targets the mentioned issue.

    If you have any further questions or need assistance with your upgrade, please don't hesitate to contact our Support team at support@luciq.ai

Did this answer your question?