Error Tracking Android
PostHogOfficialCreated by PostHog
- Skill
- Tool integration
- Data and AI
- MIT
- No issues found
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
Download the skill as a ZIP:
https://autogineer.com/agent-skills/posthog/error-tracking-android/downloadUnzip 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 - docsreferences/fingerprints.md- Fingerprints - docsreferences/alerts.md- Send error tracking alerts - docsreferences/monitoring.md- Monitor and search issues - docsreferences/assigning-issues.md- Assign issues to teammates - docsreferences/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'sonCreate()method, so it's initialized as early as possible and only once.Initialize PostHog in the Application class's
onCreate()methodEnsure every activity has a
android:labelto accurately track screen views.
Files
- ATTRIBUTION.mdAdded by AutoGineer966 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md1.8 KiB
- references/alerts.md4.1 KiB
- references/android.md3.9 KiB
- references/assigning-issues.md5.5 KiB
- references/fingerprints.md3.4 KiB
- references/monitoring.md8.6 KiB
- references/upload-source-maps.md2.7 KiB
references/assigning-issues.md
Assign issues to teammates - Docs
Error tracking enables you to assign issues to specific PostHog roles or teammates. This helps your team find relevant issues through filtering. You can also set up team-specific alerting to notify them when assigned issues are created or reopened.
Assign issues
You can manually assign issues as you triage them in the UI. This can be done both in the issue list and issue detail pages.
Image: Error tracking assignment UIImage: Error tracking assignment UI
In your error tracking issue list, click the unassigned selector under each issue to assign it to a role or user.
On the detail page of each issue, click the Assignee selector to assign it to a role or user.
Want to assign issues to a team rather than an individual teammate? You can create a role in your project settings.
Image: Error tracking role assigneesImage: Error tracking role assignees
Automatic issue assignment
You can set up automatic issue assignment through a set of rules. This can be configured in the error tracking settings using auto assignment rules.
Image: Error tracking auto assignment rulesImage: Error tracking auto assignment rules
Assignment conditions are evaluated against the properties of the exception event that created the issue. Because assignment rules are evaluated during ingestion, the stack trace (if present) will be unminified, which enables filtering on exception properties such as function name and source file.
Issues can be automatically assigned to a role or user by configuring a set of filters. These filters can be configured to match any or all of the criteria.
You can configure automatic assignment to filter on any event property in PostHog. When there are multiple values for a property, the filters return true if it matches any of the values. For example, if you have multiple exception_functions values, the filters returns true if it matches any of the functions.
Here are some common properties you can filter on:
| Property | Event property | Description |
|---|---|---|
| Exception type | $exception_types | The type of exception(s) that occurred |
| Exception message | $exception_values | The message(s) detected on the error |
| Exception function | $exception_functions | The function(s) where the exception occurred |
| Exception source | $exception_sources | The source file(s) where the exception occurred |
| Exception was handled | $exception_handled | Whether the exception was handled by the application |
| Device type | $device_type | The type of device that the error occurred on |
| Browser | $browser | The browser that the error occurred in |
| Current URL | $current_url | The URL that the error occurred on |
| Feature flag | $feature_flag | The feature flag that the error occurred on |
You can also set custom properties on the error tracking event to filter on. For example, setting a custom params_received property to provide more context or debug information.
Order of issue assignment rules
Issue assignment filters are evaluated in the order they are configured. They can also be reordered once created. The first filter that matches is used to assign the issue. This means you should configure the most specific filters first, and then the more general filters later.
Disabled assignment rules
Assignment rules can become disabled if an error occurs during ingestion. When a rule is disabled, a banner displays the original error message. To re-enable the rule, edit it to fix the problem and save your changes. If the issue persists, reach out to support.
Alerting based on assignment
A common use case for automatic issue assignment is to alert assignees of new issues. Once the issues are automatically assigned, you can set up alerts to notify the assignee. See the alerts guide for more information.
Create external issues
You can also create issues in external tracking systems like GitHub Issues, Linear, GitLab, or Jira.
First, set up an integration with your tracking system. Then, from an issue's details page, under External references, click Create issue.
Image: Error tracking create issue in external tracking systemImage: Error tracking create issue in external tracking system
The new issue will have a partial stack trace and a link to the issue in PostHog.
If you use another issue tracking system and would like to request it, 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