# Flutter error tracking installation - Docs
1. 1
## Install the package
Required
Add the PostHog Flutter SDK to your `pubspec.yaml`:
pubspec.yaml
PostHog AI
```yaml
posthog_flutter: ^5.0.0
```
2. 2
## Platform setup
Required
## Tab
Add these values to your `AndroidManifest.xml`:
android/app/src/main/AndroidManifest.xml
PostHog AI
```xml
[...]
```
Update the minimum Android SDK version to **21** in `android/app/build.gradle`:
android/app/build.gradle
PostHog AI
```groovy
defaultConfig {
minSdkVersion 21
// rest of your config
}
```
## Tab
Add these values to your `Info.plist`:
ios/Runner/Info.plist
PostHog AI
```xml
[...]
com.posthog.posthog.API_KEY
com.posthog.posthog.POSTHOG_HOST
https://us.i.posthog.com
com.posthog.posthog.CAPTURE_APPLICATION_LIFECYCLE_EVENTS
com.posthog.posthog.DEBUG
```
Update the minimum platform version to iOS 13.0 in your `Podfile`:
Podfile
PostHog AI
```ruby
platform :ios, '13.0'
# rest of your config
```
## Tab
Add these values in `index.html`:
web/index.html
PostHog AI
```html
...
...
```
3. 3
## Send events
Recommended
Once installed, PostHog will automatically start capturing events. You can also manually send events to test your integration:
Dart
PostHog AI
```dart
import 'package:posthog_flutter/posthog_flutter.dart';
await Posthog().capture(
eventName: 'button_clicked',
properties: {
'button_name': 'signup'
}
);
```
4. 4
## Set up exception autocapture
Recommended
**Client-side configuration only**
This configuration is client-side only. Support for remote configuration in the [error tracking settings](https://app.posthog.com/settings/project-error-tracking#exception-autocapture) will be added in a future release.
You can autocapture exceptions by configuring the `errorTrackingConfig` when setting up PostHog:
Dart
PostHog AI
```dart
final config = PostHogConfig('');
// Enable exception autocapture
config.errorTrackingConfig.captureFlutterErrors = true;
config.errorTrackingConfig.capturePlatformDispatcherErrors = true;
config.errorTrackingConfig.captureIsolateErrors = true;
// Requires SDK version 5.22.0 or higher
config.errorTrackingConfig.captureNativeExceptions = true;
config.errorTrackingConfig.captureSilentFlutterErrors = false;
await Posthog().setup(config);
```
**Configuration options:**
| Option | Description |
| --- | --- |
| captureFlutterErrors | Captures Flutter framework errors (FlutterError.onError) |
| capturePlatformDispatcherErrors | Captures Dart runtime errors (PlatformDispatcher.onError). Web not supported. |
| captureIsolateErrors | Captures errors from main isolate. Web not supported. |
| captureNativeExceptions | Captures native exceptions. Android (Java/Kotlin) and Apple platforms (iOS, macOS, tvOS). |
| captureSilentFlutterErrors | Captures Flutter errors that are marked as silent. Default: false. |
5. 5
## Manually capture exceptions
Optional
### Basic usage
You can manually capture exceptions using the `captureException` method:
Dart
PostHog AI
```dart
try {
// Your awesome code that may throw
await someRiskyOperation();
} catch (exception, stackTrace) {
// Capture the exception with PostHog
await Posthog().captureException(
error: exception,
stackTrace: stackTrace,
properties: {
'user_action': 'button_press',
'feature_name': 'data_sync',
},
);
}
```
This is helpful if you've built your own error handling logic or want to capture exceptions that are handled by your application code.
### Error tracking configuration
You can configure error tracking behavior when setting up PostHog:
**Flutter web apps use minified stack trace frames**
Flutter web apps generate minified stack trace frames by default, which may cause the configurations below to behave differently or not work as expected.
Dart
PostHog AI
```dart
final config = PostHogConfig('');
// Configure error tracking
config.errorTrackingConfig.inAppIncludes.add('package:your_app');
config.errorTrackingConfig.inAppExcludes.add('package:third_party_lib');
config.errorTrackingConfig.inAppByDefault = true;
await Posthog().setup(config);
```
**Configuration options:**
| Option | Description |
| --- | --- |
| inAppIncludes | List of package names to be considered inApp frames (takes precedence over excludes) |
| inAppExcludes | List of package names to be excluded from inApp frames |
| inAppByDefault | Whether frames are considered inApp by default when their origin cannot be determined |
`inApp` frames are stack trace frames that belong to your application code (as opposed to third-party libraries or system code). These are highlighted in the PostHog error tracking interface to help you focus on the relevant parts of the stack trace.
6. 6
## Future features
Optional
We currently don't support the following features:
- No de-obfuscating stacktraces from obfuscated builds ([\--obfuscate](https://docs.flutter.dev/deployment/obfuscate) and [\--split-debug-info](https://docs.flutter.dev/deployment/obfuscate)) for Dart code
- No [Source code context](/docs/error-tracking/stack-traces.md) associated with an exception (native Android Java/Kotlin errors and Flutter web only)
- No native C/C++ exception capture on Android (Java/Kotlin only)
- No background isolate error capture
For symbolicated stack traces on native platforms, see the [Flutter debug symbols guide](/docs/error-tracking/upload-source-maps/flutter.md).
These features will be added in future releases. We recommend you stay up to date with the latest version of the PostHog Flutter SDK.
7. ## Verify error tracking
Recommended
*Confirm events are being sent to PostHog*
Before proceeding, let's make sure exception events are being captured and sent to PostHog. You should see events appear in the activity feed.
[Check for exceptions in PostHog](https://app.posthog.com/activity/explore)
8. 7
## Upload source maps
Required
Great, you're capturing exceptions! If you serve minified bundles, the next step is to upload source maps to generate accurate stack traces.
Let's continue to the next section.
[Upload source maps](/docs/error-tracking/upload-source-maps/flutter.md)
### Community questions
Ask a question
### Was this page useful?
HelpfulCould be better