Integrate Luciq on Android

Integrate the Luciq SDK into your Android app step by step. Enable bug reporting and crash reporting with our comprehensive Android setup guide.

Compile SDK Version

Please note that the compileSDKVersion should be v29 or above, otherwise you may run into build errors.

Get started in seconds

Option 1 — Set up with an AI coding agent (recommended)

In your AI editor, paste:

Set up Luciq SDK in this project in one shot!
1. Install the Luciq agent skills: `npx luciq-skills install`
2. Setup and authenticate Luciq MCP server to this project
3. Add the Luciq SDK to this project

Check the skills and MCP docs for more details.

Option 2 — Install manually

This installation process will install the Luciq SDK that supports Bug Reporting, Crash Reporting and App Performance Monitoring.

Gradle

Add this line to your build.gradle file.

Gradle

implementation 'ai.luciq.library:luciq:19.6.0' 

Maven

Maven

<dependency>
      <groupId>ai.luciq.library</groupId>
      <artifactId>luciq</artifactId>
      <version>19.6.0</version>
</dependency>

Using Luciq

In your Application class add this line to your onCreate method. This initializes Luciq with the default invocation event, Shake.

Kotlin

Luciq.Builder(this, "APP_TOKEN").build()

Java

new Luciq.Builder(this, "APP_TOKEN").build();

Initializing Luciq in your application can also be done using one or multiple invocation events. All possible invocation events are explained in the invocation section.

Kotlin

Luciq.Builder(this, "APP_TOKEN")
            .setInvocationEvents(LuciqInvocationEvent.SHAKE, LuciqInvocationEvent.FLOATING_BUTTON)
            .build()

Java

new Luciq.Builder(this, "APP_TOKEN")
	.setInvocationEvents(LuciqInvocationEvent.SHAKE, LuciqInvocationEvent.SCREENSHOT)
	.build();

You can find your app token by selecting SDK Integration in the Settings menu of your Luciq dashboard.

Permissions

Permissions are automatically added to your AndroidManifest.xml file. Some of them are required to be able to fetch information like network and WiFi connection. Others are used to allow your users to attach images, videos, and audio recordings. In general, permission requests don't appear unless your user attempts to use a feature requiring a permission.

The only exception is if you set the invocation event to be a Screenshot. In that case, the storage permission will be requested when your application launches. The screenshot invocation is a special case because there is no native event that tells the SDK that a screenshot has been captured. The only way to know is to monitor the screenshots directory. The SDK is invoked when a screenshot is added to the directory while your application is active.

XML

<uses-permission android:name=“android.permission.ACCESS_NETWORK_STATE” />
<uses-permission android:name=“android.permission.WRITE_EXTERNAL_STORAGE” />
<uses-permission android:name=“android.permission.READ_EXTERNAL_STORAGE” />
<uses-permission android:name=“android.permission.ACCESS_WIFI_STATE” />
<uses-permission android:name=“android.permission.RECORD_AUDIO” />
<uses-permission android:name=“android.permission.MODIFY_AUDIO_SETTINGS” />
<uses-permission android:name=“android.permission.INTERNET” />
<uses-permission android:name=“android.permission.WAKE_LOCK” />

You can remove any of the permissions if you will not be using the feature associated with it, as in the following example.

XML

<uses-permission android:name=“android.permission.WRITE_EXTERNAL_STORAGE” tools:node=“remove”/>

Required Permissions

There are a few permissions that are always required and cannot be removed. These permissions are: <uses-permission android:name=“android.permission.WAKE_LOCK”/> <uses-permission android:name=“android.permission.INTERNET”/>

16KB Compatibility

From Android 15 (API 35), native (.so) libraries must support 16KB page sizes. Luciq supports this starting from version 13.4.0. Please upgrade if your app targets Android 15+ to avoid crashes. Learn more.