AutoGineer
Generated banner for Error Tracking Android
Generated logo for Error Tracking Android

Error Tracking Android

PostHogOfficialCreated by PostHog

  • Skill
  • Tool integration
  • Data and AI
  • MIT
  • No issues found
Download ZIP

From the author

PostHog error tracking for Android
— the description by PostHog

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides guidance on integrating the PostHog Android SDK to enable automated and manual error tracking. It covers installation, configuration, and best practices for capturing exceptions in Android applications, ensuring that developers can monitor application stability and resolve issues effectively.

What it does

  • Installs the PostHog Android SDK dependency.
  • Configures SDK initialization within the Application class.
  • Enables automatic exception capture for uncaught errors.
  • Supports manual exception capture for custom error handling.
  • Provides instructions for uploading source maps to resolve stack traces.
  • Explains how to set up alerts for error spikes and new issues.

When to use it

  • When you need to monitor runtime exceptions in an Android application.
  • When you want to automate the collection of crash reports.
  • When you need to integrate error tracking with existing PostHog analytics.
  • When you need to set up alerts for critical application errors.

Advantages

  • Centralizes error tracking within the existing PostHog ecosystem.
  • Supports both automated and manual error reporting.
  • Provides clear guidelines for maintaining clean, non-intrusive error handling code.
  • Enables actionable alerting based on error volume and issue status.

Usage examples

“How do I initialize PostHog for error tracking in my Android app?”
The agent provides the code to set up PostHogAndroidConfig and call PostHogAndroid.setup() within the Application class's onCreate() method.
“How can I capture an error manually in my catch block?”
The agent shows how to use the PostHog.captureException() method to log specific exceptions handled by your application logic.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/posthog/error-tracking-android/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip error-tracking-android.zip -d .agents/skills

Documentation by PostHog

PostHog error tracking for Android

This skill helps you add PostHog error tracking to Android applications.

Reference files

  • references/android.md - Android error tracking installation - docs

  • references/fingerprints.md - Fingerprints - docs

  • references/alerts.md - Send error tracking alerts - docs

  • references/monitoring.md - Monitor and search issues - docs

  • references/assigning-issues.md - Assign issues to teammates - docs

  • references/upload-source-maps.md - Upload source maps - docs

Consult the documentation for API details and framework-specific patterns.

Key principles

  • Environment variables: Always use environment variables for PostHog keys and host URLs. Never hardcode them.

  • Minimal changes: Add error tracking alongside existing error handling. Don't replace or restructure existing error handling code.

  • Autocapture first: Enable exception autocapture in the SDK initialization before adding manual captures.

  • Source maps: Upload source maps so stack traces resolve to original source code, not minified bundles.

  • Manual capture for boundaries: Use captureException() at error boundaries and catch blocks for errors that don't propagate to the global handler.

Framework guidelines

  • Adapt dependency configuration to the appropriate build.gradle(.kts) file according to the project gradle version

  • Call PostHogAndroid.setup() only once in the Application class's onCreate() method, so it's initialized as early as possible and only once.

  • Initialize PostHog in the Application class's onCreate() method

  • Ensure every activity has a android:label to accurately track screen views.

Files

references/alerts.md

Send error tracking alerts - Docs

To stay on top of issues, you can set up alerts. These enable you to post to Slack, Discord, Teams, or an HTTP Webhook when an issue is created or reopened.

Issue created or reopened

To alert when an issue is created or reopened, go to error tracking's configuration page and click Alerting. This shows you a list of existing alerts. Clicking New notification brings you to a page to create a new one.

Image: Error tracking alertingImage: Error tracking alerting

Choosing an option brings you to a page to configure the alert. This may require setting up the Slack integration or pasting in a webhook URL. Once done, you can test the alert by clicking Test function and then finalize by clicking Create & enable.

This will then send alerts to your chosen destination when an issue is created or reopened like this:

Issue properties and assignments

You can filter an alert based on the properties of an issue. This is useful for notifying a specific team when they have been auto assigned an issue using auto assignment rules.

Image: Error tracking alert assignee filteringImage: Error tracking alert assignee filtering

Spike alerts

PostHog can also alert you when an existing issue suddenly spikes in volume - for example, after a bad deploy. This works differently from issue-created alerts. Instead of triggering when a new issue is first seen, spike alerts fire when an issue's error rate significantly exceeds its historical baseline.

See the spike detection guide to learn how it works and how to configure it.

Other alerting options

Since error tracking works by capturing $exception events, PostHog features that trigger by events can play a role in alerts too.

Real time destinations

The first way is using real time destinations. This enables you to send events (like $exception) to other tools as soon as they are ingested.

To create a real time destination, go to the data pipelines tab in PostHog, click + New, and then select Destination. Choose your destination and press + Create.

On the destination creation screen, make sure to add an event matcher for the $exception event, filter for the properties you want, and set the trigger options.

Image: Real time destinationImage: Real time destination

Check out our real time destinations docs for more information.

Trend alerts

You can also visualize your $exception events using trends. Once you create a trend insight, click the Alerts button at the top of the insight and then New alert.

Here you can set alerts for event volume value, increase, or decrease.

Image: Insight alertImage: Insight alert

This sends an email notification to the user you choose. Check out our alerts docs for more information.

Can't find your alert?

If you'd like a destination to be added that we don't yet support, let us know in-app.

Community questions

Ask a question

Was this page useful?

HelpfulCould be better

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
PostHog
Publisher
PostHog (Official)
Source
PostHog/skills · skills/posthog/error-tracking/skills/android · commit a5d30e7
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Also distributed in
PostHog/skills

AutoGineer is not affiliated with or endorsed by PostHog or PostHog.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download error-tracking-android.zip