Instabug Integration for Mobile App Bug Tracking

A tester finds a bug. They take a screenshot in Telegram and write a text description of what they did. The developer cannot reproduce—no logs, device info, or network requests. According to our data, up to 70% of bug‑fixing time is spent gathering context. Instead of back‑and‑forth, we integrate Instabug: shake‑to‑report, annotated screenshots, logs, device and session data. After integration, bug report processing time drops by 3–5 times. Instabug is 3–5 times faster than traditional debugging methods, reducing debugging costs by 60–70%. Our team, with 8+ years of mobile development experience and over 50 successful Instabug integrations, has served clients in FinTech, E‑commerce, and HealthTech since 2018. We offer a free project evaluation that guarantees a seamless setup—contact us.

Data automatically attached to a report

Instabug automatically captures up to 100 recent user steps (session replay), up to 50 network requests with headers and bodies, device info (model, OS, app version), and memory/CPU usage over the last 30 seconds. The tester only needs to describe what went wrong—within 5 minutes the developer sees the full picture. In 90% of cases, the report contains enough information to reproduce without further clarification. This comprehensive Instabug log collection is the cornerstone of effective mobile bug tracking.

Platform support comparison for Instabug

Problems Instabug solves

Instabug is indispensable when a bug only appears on a rare configuration: iOS 16.3 with locale en‑US or Android 12 with Cyrillic input. The developer immediately sees device info and logs. It is especially useful for network race conditions: Instabug saves all requests even if the connection drops. Our experience shows a 60–70% reduction in bug report time. For example, a FinTech client had a bug that only appeared on Android 12 with Cyrillic input in the amount field. Instabug captured device info and the network request—turns out the server returned 400 due to incorrect encoding. Without Instabug, debugging would have taken 2 days; with it, 2 hours. This proven debugging time reduction is why we recommend Instabug setup for all mobile apps.

How to integrate Instabug

Step 1: Add SDK to project

For iOS, use CocoaPods or SPM; for Android, Gradle. Instabug supports Swift 5.9+, Kotlin 1.9+, and Flutter/React Native via official plugins. For Android, add the following ProGuard rules to keep Instabug classes:

-keep class com.instabug.** { *; } 

Step 2: Initialize with token

iOS (Swift):

// AppDelegate.swift import Instabug func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool { Instabug.start(withToken: "YOUR_APP_TOKEN", invocationEvents: [.shake, .screenshot]) Instabug.welcomeMessageMode = .disabled // remove onboarding for testers NetworkLogger.enabled = true return true } 

Android (Kotlin):

// Application class override fun onCreate() { super.onCreate() Instabug.Builder(this, "YOUR_APP_TOKEN") .setInvocationEvents(InstabugInvocationEvent.SHAKE, InstabugInvocationEvent.SCREENSHOT_GESTURE) .build() NetworkLogger.setEnabled(true) } 

For intercepting network requests on Android—OkHttp interceptor:

val client = OkHttpClient.Builder() .addInterceptor(InstabugOkhttpInterceptor()) .build() 

Step 3: Configure obfuscation of sensitive data

Instabug logs network requests fully. If your API passes passwords or tokens in the body, configure a blacklist using NetworkLogger.addIgnoredURL with the endpoints that require masking. For finer control, implement a custom response sanitizer to mask specific fields. This sensitive data obfuscation prevents leakage of passwords, tokens, and personal data.

Step 4: Configure environments

Use separate tokens for Debug, Staging, and Release. Enable full logging and session replay in Debug, and only crash reports in Release. This reduces noise and speeds up critical bug detection.

Importance of configuring Instabug for your workflow

Without proper configuration, Instabug can clutter the dashboard with test reports. Setting up a report template with required fields (priority, component, steps to reproduce) is key to order. Integration with Jira, GitHub Issues, or Linear automatically creates tickets with attached logs. We configure the report template for your workflow and train the team. For example, Instabug Jira integration saves hours of manual ticket creation.

Instabug integration with your stack

Instabug adapts to your development cycle. We configure it for CI/CD: separate configs for Staging and Release, automatic enabling of NetworkLogger only for internal builds. This reduces noise and speeds up critical bug detection.

What's included in Instabug integration

• SDK installation and configuration for iOS / Android / Flutter / React Native
• Initialization setup for all environments (Debug, Staging, Release)
• Network request interception (OkHttp / URLSession)
• Obfuscation of sensitive fields (passwords, tokens)
• Integration with your bug tracker (Jira, Linear, GitHub Issues)
• Report template and custom invocation events configuration
• Documentation for the team on using Instabug
• Post-implementation support

Timelines and cost

Basic integration starts at $500 and takes from 1 day. Extended integration (with tracker integration, obfuscation, environment setup) costs up to $2500 and takes up to 5 days. Cost is calculated individually based on configuration complexity. Request a consultation—we will evaluate your project and propose the optimal solution. Our guaranteed process ensures you reduce debugging time by at least 3x.