iOS, Android, Flutter, React Native

Install one package per platform

Each platform has a Blipit package that takes the public key and project id, all built on Blipit's own core with no third-party crash library inside: blipit-android v0.7.5, blipit-swift 0.8.0, @blipit/react-native 0.6.3 and blipit_flutter 0.5.3. Crashes, ANRs, hangs and uncaught exceptions are reported on their own, written to disk first and sent on the next launch, and an offline queue keeps reports until the network is back. Keep debug symbols for native crashes, since symbol files are not read yet.

Copy a prompt for your AI assistantPaste it into Claude Code, Cursor or any AI coding assistant. It carries the steps and the code. In app.blipit.io, API keys, the same prompt comes with your key filled in.
Video: Install Blipit in any stack, from 1:56

1Get your keys

Sign in at app.blipit.io and open API keys in the sidebar, then your project. Every project has two keys. The public key starts with blipit_pk_: it goes in browser and app code, can only send events, and is safe for anyone to see. The secret key starts with blipit_sk_: it stays on your server or in Odoo, never in a browser, because it can also read and change issues. The secret key is shown only once, right after it is created, so copy it then; if you lose it, press Create a new secret key, and the old one stops working at once. Some SDKs also need the project id, shown on the same page.

API keys in app.blipit.io: the public key (blipit_pk_) for browser code and the secret key (blipit_sk_) for servers and Odoo.
API keys in app.blipit.io: the public key (blipit_pk_) for browser code and the secret key (blipit_sk_) for servers and Odoo.
A new secret key is shown once. Copy it now: it is stored hashed and cannot be shown again.
A new secret key is shown once. Copy it now: it is stored hashed and cannot be shown again.

2React Native

The package links a small native module that starts Blipit's own Android and iOS SDKs for native crashes; its Gradle file adds the JitPack repository on its own. Wrap the root component so render errors are reported too.

sh
npm install @blipit/react-native
npx pod-install
tsx
import * as Blipit from "@blipit/react-native";

Blipit.init({ key: "<public key>", project: <project id>, environment: "production", release: "myapp@1.4.2" });

export default Blipit.wrap(App);

3Flutter

Replace runApp in main.dart with Blipit.init. The plugin starts Blipit's own Android and iOS SDKs for native crashes, and Flutter framework errors and uncaught async errors are reported on their own.

sh
flutter pub add blipit_flutter
main.dart
import 'package:blipit_flutter/blipit_flutter.dart';

Future<void> main() async {
  await Blipit.init(
    key: '<public key>',
    project: <project id>,
    environment: 'production',
    release: 'myapp@1.4.2',
    appRunner: () => runApp(const MyApp()),
  );
}

4iOS and macOS (Swift Package)

In Xcode, File, Add Package Dependencies, and enter the repository URL; or add it to Package.swift and add BlipitSwift to your target. With CocoaPods, use the BlipitSwift pod. Then call start once at launch. With an empty key or project id, start prints a warning and returns false instead of crashing the app.

Package.swift
.package(url: "https://github.com/blipit-io/blipit-swift", from: "0.8.0")
Podfile
pod "BlipitSwift", "~> 0.8.0"
swift
import BlipitSwift

Blipit.start(key: "<public key>", project: "<project id>", environment: "production", release: "myapp@1.4.2")

5Android

Add JitPack to the repositories in settings.gradle.kts, the dependency to the app module, and call init in Application.onCreate.

settings.gradle.kts
dependencyResolutionManagement {
    repositories {
        google()
        mavenCentral()
        maven("https://jitpack.io")
    }
}
build.gradle.kts (app)
implementation("com.github.blipit-io:blipit-android:v0.7.5")
kotlin
import io.blipit.android.Blipit

class App : Application() {
    override fun onCreate() {
        super.onCreate()
        Blipit.init(this) {
            key = "<public key>"
            project = "<project id>"
            environment = "production"
            release = "myapp@1.4.2"
        }
    }
}

6Where the key goes in an app

Apps ship the public key and the project id inside the app, which is fine: the public key can only send events. Never put the secret key in an app. Pass them in at build time so they stay out of your repository.

Flutter
flutter run --dart-define=BLIPIT_KEY=blipit_pk_your_public_key --dart-define=BLIPIT_PROJECT=12
main.dart
const key = String.fromEnvironment('BLIPIT_KEY');
const project = int.fromEnvironment('BLIPIT_PROJECT');
Expo (.env)
EXPO_PUBLIC_BLIPIT_KEY=blipit_pk_your_public_key
EXPO_PUBLIC_BLIPIT_PROJECT=12
Android build.gradle.kts
buildConfigField("String", "BLIPIT_KEY", "\"${project.findProperty("blipitKey")}\"")
iOS xcconfig
BLIPIT_KEY = blipit_pk_your_public_key

7Bug reports in apps

Call showReport from your own menu item, or turn on the floating Report a bug button. The reporter first asks how to show the problem: take a screenshot, record the screen (iOS) or just describe it. The screenshot opens full screen with the tools above and below it, never on top; pinch or double-tap to zoom, mark the problem, then add a title and what happened and send. Reports arrive under Bug reports with the device details. React Native needs react-native-view-shot for screenshots.

React Native
import * as Blipit from "@blipit/react-native";

export default function Root() {
  return (
    <Blipit.BlipitReporter showButton>
      <App />
    </Blipit.BlipitReporter>
  );
}

Blipit.showReport();
Flutter
appRunner: () => runApp(const BlipitReporter(showButton: true, child: MyApp())),

Blipit.showReport();
iOS
Blipit.showReportButton()

Blipit.showReport()
Android
Blipit.showReportButton()

Blipit.showReport()

8Report from the screen with the bug

A Report a bug item in a menu such as Profile captures the menu, not the problem. Turn on the ways that start from the screen itself; they are off by default and need no permission prompt. shakeToReport opens the reporter when the phone is shaken. screenshotToReport asks "Report a bug with this screen?" after a normal screenshot and attaches Blipit's own capture (iOS, and Android 14 and newer). twoFingerReport opens it after a two-finger press and hold of about a second, without blocking the app's own touches. reportAfterCrash asks what the person was doing on the first launch after a crash and links the report to that crash. screenPicker, on by default, lets someone who opens the reporter from a menu pick which of the last few screens the bug is on: the snapshots stay in memory on the device and only the chosen one is uploaded. Jetpack Compose and SwiftUI apps name their screens with setScreen.

Android
Blipit.init(this) {
    key = "<public key>"
    project = "<project id>"
    shakeToReport = true
    screenshotToReport = true
    twoFingerReport = true
    reportAfterCrash = true
}

navController.addOnDestinationChangedListener { _, destination, _ ->
    Blipit.setScreen(destination.route ?: "screen")
}
iOS
Blipit.start(key: "<public key>", project: "<project id>") { options in
    options.shakeToReport = true
    options.screenshotToReport = true
    options.twoFingerReport = true
    options.reportAfterCrash = true
}

CartView().onAppear { Blipit.setScreen("Cart") }
React Native
Blipit.init({
  key: "<public key>",
  project: <project id>,
  shakeToReport: true,
  screenshotToReport: true,
  twoFingerReport: true,
  reportAfterCrash: true,
});

<NavigationContainer ref={navigation} onReady={() => Blipit.trackNavigation(navigation)}>
Flutter
await Blipit.init(
  key: '<public key>',
  project: <project id>,
  shakeToReport: true,
  screenshotToReport: true,
  twoFingerReport: true,
  reportAfterCrash: true,
  appRunner: () => runApp(BlipitReporter(child: MaterialApp(navigatorObservers: [BlipitNavigatorObserver()], home: const Home()))),
);

9Floating button for testers only

In app.blipit.io, open the project and, under the bug report button settings, set Floating button in phone apps to Everyone or Testers only, with one user id or email per tester. The app sends the person it set with setUser and Blipit answers only yes or no, so the tester list never ships inside the app. Calling showReportButton (showButton on React Native and Flutter) still shows the button for everyone.

Android
Blipit.setUser(id = user.id, email = user.email)
iOS
Blipit.setUser(id: user.id, email: user.email)
React Native
Blipit.setUser({ id: user.id, email: user.email });
Flutter
Blipit.setUser(BlipitUser(id: user.id, email: user.email));

10Catch an app that gets stuck

Some failures never crash: the splash screen keeps spinning, or sign-in never comes back. Turn on waitForReady and call reportReady once the first usable screen shows. Wrap flows such as sign-in in startFlow and endFlow, and mark steps with flowStep. When one does not finish in time, Blipit opens a Stuck issue with the last step and the trail before it. Only time on screen counts, and Blipit sets the time limits. Names are sent as written, so use fixed names, never emails or other user data.

Android
Blipit.init(this) {
    key = "<public key>"
    project = "<project id>"
    waitForReady = true
}

Blipit.reportReady()

Blipit.startFlow("sign-in")
Blipit.flowStep("sign-in", "google-picker")
Blipit.endFlow("sign-in")
iOS
Blipit.start(key: "<public key>", project: "<project id>", waitForReady: true)

Blipit.reportReady()

Blipit.startFlow("sign-in")
Blipit.flowStep("sign-in", "apple-sheet")
Blipit.endFlow("sign-in")
React Native
Blipit.init({ key: "<public key>", project: <project id>, waitForReady: true });

Blipit.reportReady();

Blipit.startFlow("sign-in");
Blipit.flowStep("sign-in", "google-picker");
Blipit.endFlow("sign-in");
Flutter
await Blipit.init(key: '<public key>', project: <project id>, waitForReady: true, appRunner: () => runApp(const MyApp()));

Blipit.reportReady();

Blipit.startFlow('sign-in');
Blipit.flowStep('sign-in', 'google-picker');
Blipit.endFlow('sign-in');

11Check it works

Open Issues in app.blipit.io. The first event appears within a few seconds, grouped into an issue, and the people in charge get an email.

React Native
Blipit.captureMessage("Hello from React Native");
Flutter
await Blipit.captureMessage('Hello from Flutter');
iOS
Blipit.captureMessage("Hello from iOS")
Android
Blipit.captureMessage("Hello from Android")

Good to know

  • Manual capture on every platform: captureException, captureMessage, setUser, setTag, addBreadcrumb and captureSecurity for login attempts.
  • Expo: run npx expo prebuild or use a development build. Expo Go has no custom native code, so JavaScript errors are still reported there but native crashes are not.
  • Upgrading React Native from 0.4: uninstall the third-party monitoring package that 0.4 installed alongside it and remove its Expo config plugin; dsn() and withIdentity() are gone. Flutter from 0.3: remove that package from pubspec.yaml too; the level and user types are now BlipitLevel and BlipitUser, capture calls return the event id as a String?, and Blipit.dsn, Blipit.configure and the options: callback of init are gone. On both, tracesSampleRate is accepted but performance traces are not sent in this version.
  • Upgrading Android to v0.5.0 and iOS to 0.5.0: most apps only bump the version. Capture calls return the event id as a string, the level type is Blipit's own Level, and Blipit.dsn is gone. On Android, configure and apply are removed and the replay mask tag is now blipit-mask. On iOS, Options is Blipit's own class and beforeSend works on the event as a dictionary.
  • Store review for the report triggers: there is no new permission prompt. iOS uses UIKit shake events (not CoreMotion) and the screenshot notification, so the privacy manifest needs no new entry. On Android 14 and newer the SDK declares DETECT_SCREEN_CAPTURE, a normal permission granted at install; for Google Play Data safety nothing new is collected, because Blipit only learns that a screenshot was taken and never reads it or the gallery. Older Android versions skip screenshot to report. Huawei AppGallery builds behave the same and use no Google Play services.
  • Check the installed version with npm ls @blipit/react-native (or pnpm list @blipit/react-native). pnpm 11 waits a day before it installs a new release (minimum-release-age), so on release day pnpm add quietly installs the previous version; to get the new one at once, run pnpm add @blipit/react-native@<version> --config.minimum-release-age=0.
  • Keeping Blipit up to date: the Keeping Blipit up to date guide (docs.blipit.io/updates) explains the update banner, the emails for important releases, the notice in your development console and the update command for this platform.
  • One project per app and platform: each project picks its platform when it is created (Android, iOS, React Native, Flutter, Web, Backend or Odoo), and Blipit refuses data from any other platform with a clear error, so an iOS app and an Android app need two projects with two keys. Releases, versions, crash rates and store builds differ per platform, so mixing them in one project makes all of them wrong. A Web project also takes the server side of the same web app (the Next.js server or Node), and a React Native or Flutter project also takes its own native Android and iOS crash reports.

Stuck? Email support@blipit.io. Keys and the project id for each project are under API keys in app.blipit.io.