vybekiit 0.7.33 → 0.7.35

package/dist/global-skills/instrument-product-analytics/references/EXAMPLE-laravel.md

@@ -195,7 +195,7 @@ The `/api/test-error` endpoint demonstrates manual exception capture. Use `?capt
 ## Project Structure
 
 ```
-basics/laravel/
+example-apps/laravel/
 ├── app/
 │   ├── Http/
 │   │   ├── Controllers/
@@ -1251,7 +1251,7 @@ This document summarizes the implementation of the Laravel PostHog example appli
 ## 📁 File Structure
 
 ```
-basics/laravel/
+example-apps/laravel/
 ├── app/
 │   ├── Http/
 │   │   ├── Controllers/

package/dist/global-skills/instrument-product-analytics/references/EXAMPLE-php.md

@@ -80,7 +80,7 @@ The app tracks these events in PostHog:
 ## Code Structure
 
 ```
-basics/php/
+example-apps/php/
 ├── todo.php             # Main CLI application
 ├── composer.json        # PHP dependencies
 ├── .env.example         # Environment variable template

package/dist/global-skills/instrument-product-analytics/references/EXAMPLE-python.md

@@ -85,7 +85,7 @@ The app tracks these events in PostHog:
 ## Code Structure
 
 ```
-basics/python/
+example-apps/python/
 ├── todo.py              # Main CLI application
 ├── requirements.txt     # Python dependencies
 ├── .env.example        # Environment variable template

package/dist/global-skills/instrument-product-analytics/references/EXAMPLE-ruby.md

@@ -83,7 +83,7 @@ The app tracks these events in PostHog:
 ## Code Structure
 
 ```
-basics/ruby/
+example-apps/ruby/
 ├── todo.rb              # Main CLI application
 ├── Gemfile              # Ruby dependencies
 ├── .env.example         # Environment variable template

package/dist/global-skills/instrument-product-analytics/references/EXAMPLE-swift.md

@@ -61,7 +61,7 @@ import PostHog
 
 // The project token is a public client-side key, so it's safe to ship in the
 // binary. Replace the placeholder with your token from the PostHog project settings.
-let config = PostHogConfig(apiKey: "<your-project-token>", host: "https://us.i.posthog.com")
+let config = PostHogConfig(projectToken: "<your-project-token>", host: "https://us.i.posthog.com")
 config.captureApplicationLifecycleEvents = true
 PostHogSDK.shared.setup(config)
 ```
@@ -143,8 +143,8 @@ PostHogSDK.shared.reset()
       "kind" : "remoteSourceControl",
       "location" : "https://github.com/PostHog/posthog-ios",
       "state" : {
-        "revision" : "1783865d79a1cabc472cf2d56a1fe3f797417b52",
-        "version" : "3.40.0"
+        "revision" : "835f624c2618d72d73650d0ed0029325232f5b0a",
+        "version" : "3.92.0"
       }
     }
   ],
@@ -280,7 +280,7 @@ struct BurritoConsiderationClientApp: App {
     @State private var userState = UserState()
 
     init() {
-        let config = PostHogConfig(apiKey: posthogProjectToken, host: posthogHost)
+        let config = PostHogConfig(projectToken: posthogProjectToken, host: posthogHost)
         config.captureApplicationLifecycleEvents = true
         config.debug = true
         PostHogSDK.shared.setup(config)

package/dist/global-skills/instrument-product-analytics/references/android.md

@@ -2,6 +2,37 @@
 
 # Android
 
+Canonical URL: https://posthog.com/docs/libraries/android
+
+> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` (app host for links).
+
+## On this page
+
+- [Installation](#installation)
+- [Capturing events](#capturing-events)
+- [Identifying users](#identifying-users)
+- [Get the current user's distinct ID](#get-the-current-users-distinct-id)
+- [Tracing headers](#tracing-headers)
+- [Alias](#alias)
+- [Anonymous and identified events](#anonymous-and-identified-events)
+- [Setting person properties](#setting-person-properties)
+- [Super Properties](#super-properties)
+- [Opt out of data capture](#opt-out-of-data-capture)
+- [Flush](#flush)
+- [Reset after logout](#reset-after-logout)
+- [Feature Flags](#feature-flags)
+- [Experiments (A/B tests)](#experiments-ab-tests)
+- [Group analytics](#group-analytics)
+- [Error tracking](#error-tracking)
+- [Logs](#logs)
+- [Session replay](#session-replay)
+- [Surveys](#surveys)
+- [Offline behavior](#offline-behavior)
+- [Debug mode](#debug-mode)
+- [All configuration options](#all-configuration-options)
+- [What Android API level is required?](#what-android-api-level-is-required)
+- [Do I need to declare permissions in the AndroidManifest.xml?](#do-i-need-to-declare-permissions-in-the-androidmanifestxml)
+
 It uses an internal queue to make calls fast and non-blocking. It also batches requests and flushes asynchronously, making it perfect to use in any part of your mobile app.
 
 ## Installation
@@ -30,8 +61,6 @@ dependencies {
 
 The best place to initialize the client is in your `Application` subclass.
 
-Kotlin
-
 ```kotlin
 import android.app.Application
 import com.posthog.android.PostHogAndroid
@@ -61,8 +90,6 @@ class SampleApp : Application() {
 
 You can send custom events using `capture`:
 
-Kotlin
-
 ```kotlin
 import com.posthog.PostHog
 
@@ -73,9 +100,7 @@ PostHog.capture(event = "user_signed_up")
 
 ### Setting event properties
 
-Optionally, you can include additional information with the event by including a [properties](/docs/data/events.md#event-properties) object:
-
-Kotlin
+Optionally, you can include additional information with the event by including a [properties](https://posthog.com/docs/data/events.md#event-properties) object:
 
 ```kotlin
 import com.posthog.PostHog
@@ -99,16 +124,14 @@ PostHog autocapture automatically tracks the following events for you:
 -   **Application Installed** - when the app is installed.
 -   **Application Updated** - when the app is updated.
 -   **$screen** - when the user navigates. (if using `android.app.Activity`)
--   **$exception** - when uncaught exception autocapture is enabled. To use this, enable [Android error tracking](/docs/error-tracking/installation/android.md) and exception autocapture in the SDK config.
+-   **$exception** - when uncaught exception autocapture is enabled. To use this, enable [Android error tracking](https://posthog.com/docs/error-tracking/installation/android.md) and exception autocapture in the SDK config.
 
 ### Capturing screen views
 
-With [`captureScreenViews = true`](/docs/libraries/android.md#all-configuration-options), PostHog will try to record all screen changes automatically.
+With [`captureScreenViews = true`](https://posthog.com/docs/libraries/android.md#all-configuration-options), PostHog will try to record all screen changes automatically.
 
 The `screenTitle` will be the [`<activity>`](https://developer.android.com/guide/topics/manifest/activity-element)'s `android:label`, if not set it'll fallback to the [`<application>`](https://developer.android.com/guide/topics/manifest/application-element)'s `android:label` or the [`<activity>`](https://developer.android.com/guide/topics/manifest/activity-element)'s `android:name`.
 
-XML
-
 ```xml
 <activity
     android:name="com.example.app.ChildActivity"
@@ -121,8 +144,6 @@ If you want to manually send a new screen capture event, use the `screen` functi
 
 This function requires a `screenTitle`. You may also pass in an optional `properties` object.
 
-Kotlin
-
 ```kotlin
 import com.posthog.PostHog
 
@@ -137,17 +158,15 @@ PostHog.screen(
 
 ## Identifying users
 
-> We highly recommend reading our section on [Identifying users](/docs/integrate/identifying-users.md) to better understand how to correctly use this method.
+> We highly recommend reading our section on [Identifying users](https://posthog.com/docs/integrate/identifying-users.md) to better understand how to correctly use this method.
 
 Using `identify`, you can associate events with specific users. This enables you to gain full insights as to how they're using your product across different sessions, devices, and platforms.
 
 An `identify` call has the following arguments:
 
 -   **distinctId:** Required. A unique identifier for your user. Typically either their email or database ID.
--   **userProperties:** Optional. A dictionary with key:value pairs to set the [person properties](/docs/product-analytics/person-properties.md)
--   **userPropertiesSetOnce:** Optional. Similar to `userProperties`. [See the difference between `userProperties` and `userPropertiesSetOnce`](/docs/product-analytics/person-properties.md#what-is-the-difference-between-set-and-set_once)
-
-Kotlin
+-   **userProperties:** Optional. A dictionary with key:value pairs to set the [person properties](https://posthog.com/docs/product-analytics/person-properties.md)
+-   **userPropertiesSetOnce:** Optional. Similar to `userProperties`. [See the difference between `userProperties` and `userPropertiesSetOnce`](https://posthog.com/docs/product-analytics/person-properties.md#what-is-the-difference-between-set-and-set_once)
 
 ```kotlin
 import com.posthog.PostHog
@@ -178,8 +197,6 @@ To do this, call `distinctId()`. This returns either the ID automatically genera
 
 Use `tracingHeaders` to connect Android network requests to backend events, errors, and LLM traces captured by a server-side PostHog SDK. Tracing headers are added by the `PostHogOkHttpInterceptor`, so install the interceptor on each `OkHttpClient` whose requests should include PostHog context.
 
-Kotlin
-
 ```kotlin
 import com.posthog.PostHogOkHttpInterceptor
 import com.posthog.android.PostHogAndroid
@@ -208,8 +225,6 @@ Sometimes, you want to assign multiple distinct IDs to a single user. This is he
 
 In this case, you can use `alias` to assign another distinct ID to the same user.
 
-Kotlin
-
 ```kotlin
 /**
  * Create an alias for the current user.
@@ -217,13 +232,13 @@ Kotlin
 PostHog.alias("distinct_id")
 ```
 
-We strongly recommend reading our docs on [alias](/docs/product-analytics/identify.md#alias-assigning-multiple-distinct-ids-to-the-same-user) to best understand how to correctly use this method.
+We strongly recommend reading our docs on [alias](https://posthog.com/docs/product-analytics/identify.md#alias-assigning-multiple-distinct-ids-to-the-same-user) to best understand how to correctly use this method.
 
 ## Anonymous and identified events
 
-PostHog captures two types of events: [**anonymous** and **identified**](/docs/data/anonymous-vs-identified-events.md)
+PostHog captures two types of events: [**anonymous** and **identified**](https://posthog.com/docs/data/anonymous-vs-identified-events.md)
 
-**Identified events** enable you to attribute events to specific users, and attach [person properties](/docs/product-analytics/person-properties.md). They're best suited for logged-in users.
+**Identified events** enable you to attribute events to specific users, and attach [person properties](https://posthog.com/docs/product-analytics/person-properties.md). They're best suited for logged-in users.
 
 Scenarios where you want to capture identified events are:
 
@@ -231,7 +246,7 @@ Scenarios where you want to capture identified events are:
 -   Doing user segmented product analysis
 -   Growth and marketing teams wanting to analyze the *complete* conversion lifecycle
 
-**Anonymous events** are events without individually identifiable data. They're best suited for [web analytics](/docs/web-analytics.md) or apps where users aren't logged in.
+**Anonymous events** are events without individually identifiable data. They're best suited for [web analytics](https://posthog.com/docs/web-analytics.md) or apps where users aren't logged in.
 
 Scenarios where you want to capture anonymous events are:
 
@@ -239,15 +254,15 @@ Scenarios where you want to capture anonymous events are:
 -   Content-focused sites
 -   B2C apps where users don't sign up or log in
 
-Under the hood, the key difference between identified and anonymous events is that for identified events we create a [person profile](/docs/data/persons.md) for the user, whereas for anonymous events we do not.
+Under the hood, the key difference between identified and anonymous events is that for identified events we create a [person profile](https://posthog.com/docs/data/persons.md) for the user, whereas for anonymous events we do not.
 
 > **Important:** Due to the reduced cost of processing them, anonymous events can be up to 4x cheaper than identified ones, so we recommended you only capture identified events when needed.
 
 ### How to capture anonymous events
 
-The Android SDK captures anonymous events by default. However, this may change depending on your `personProfiles` [config](/docs/libraries/android.md#all-configuration-options) when initializing PostHog:
+The Android SDK captures anonymous events by default. However, this may change depending on your `personProfiles` [config](https://posthog.com/docs/libraries/android.md#all-configuration-options) when initializing PostHog:
 
-1.  `personProfiles = PersonProfiles.IDENTIFIED_ONLY` *(recommended)* *(default)* - Anonymous events are captured by default. PostHog only captures identified events for users where [person profiles](/docs/data/persons.md) have already been created.
+1.  `personProfiles = PersonProfiles.IDENTIFIED_ONLY` *(recommended)* *(default)* - Anonymous events are captured by default. PostHog only captures identified events for users where [person profiles](https://posthog.com/docs/data/persons.md) have already been created.
 
 2.  `personProfiles = PersonProfiles.ALWAYS` - Capture identified events for all events.
 
@@ -255,8 +270,6 @@ The Android SDK captures anonymous events by default. However, this may change d
 
 For example:
 
-Kotlin
-
 ```kotlin
 val config = PostHogAndroidConfig(
    apiKey = POSTHOG_API_KEY,
@@ -268,24 +281,22 @@ val config = PostHogAndroidConfig(
 
 ### How to capture identified events
 
-If you've set the [`personProfiles` config](/docs/libraries/android.md#all-configuration-options) to `IDENTIFIED_ONLY` (the default option), anonymous events are captured by default. Then, to capture identified events, call any of the following functions:
+If you've set the [`personProfiles` config](https://posthog.com/docs/libraries/android.md#all-configuration-options) to `IDENTIFIED_ONLY` (the default option), anonymous events are captured by default. Then, to capture identified events, call any of the following functions:
 
--   [`identify()`](/docs/product-analytics/identify.md)
--   [`alias()`](/docs/product-analytics/identify.md#alias-assigning-multiple-distinct-ids-to-the-same-user)
--   [`group()`](/docs/product-analytics/group-analytics.md)
+-   [`identify()`](https://posthog.com/docs/product-analytics/identify.md)
+-   [`alias()`](https://posthog.com/docs/product-analytics/identify.md#alias-assigning-multiple-distinct-ids-to-the-same-user)
+-   [`group()`](https://posthog.com/docs/product-analytics/group-analytics.md)
 
-When you call any of these functions, it creates a [person profile](/docs/data/persons.md) for the user. Once this profile is created, all subsequent events for this user will be captured as identified events.
+When you call any of these functions, it creates a [person profile](https://posthog.com/docs/data/persons.md) for the user. Once this profile is created, all subsequent events for this user will be captured as identified events.
 
 Alternatively, you can set `personProfiles` to `ALWAYS` to capture identified events by default.
 
 ## Setting person properties
 
-To set [properties](/docs/product-analytics/person-properties.md) on your users via an event, you can leverage the event properties `userProperties` and `userPropertiesSetOnce`.
+To set [properties](https://posthog.com/docs/product-analytics/person-properties.md) on your users via an event, you can leverage the event properties `userProperties` and `userPropertiesSetOnce`.
 
 When capturing an event, you can pass a property called `userProperties` as an event property, and specify its value to be an object with properties to be set on the user that will be associated with the user who triggered the event.
 
-Kotlin
-
 ```kotlin
 import com.posthog.PostHog
 
@@ -301,8 +312,6 @@ PostHog.capture(
 
 `userPropertiesSetOnce` works just like `userProperties`, except that it will **only set the property if the user doesn't already have that property set**.
 
-Kotlin
-
 ```kotlin
 import com.posthog.PostHog
 
@@ -324,8 +333,6 @@ They are set using `PostHog.register`, which takes a key and value, and they per
 
 For example, take a look at the following call:
 
-Kotlin
-
 ```kotlin
 import com.posthog.PostHog
 
@@ -340,8 +347,6 @@ However, please note that this does not store properties against the User, only
 
 Super Properties are persisted across sessions so you have to explicitly remove them if they are no longer relevant. In order to stop sending a Super Property with events, you can use `PostHog.unregister`, like so:
 
-Kotlin
-
 ```kotlin
 import com.posthog.PostHog
 
@@ -358,8 +363,6 @@ You can completely opt-out users from data capture. To do this, there are two op
 
 1.  Opt users out by default by setting `optOut` to `true` in your PostHog config:
 
-Kotlin
-
 ```kotlin
 val config = PostHogAndroidConfig(
     apiKey = "<ph_project_token>",
@@ -371,24 +374,18 @@ PostHogAndroid.setup(this, config)
 
 2.  Opt users out on a per-person basis by calling `optOut()`:
 
-Kotlin
-
 ```kotlin
 PostHog.optOut()
 ```
 
 Similarly, you can opt users in:
 
-Kotlin
-
 ```kotlin
 PostHog.optIn()
 ```
 
 To check if a user is opted out:
 
-Kotlin
-
 ```kotlin
 PostHog.isOptOut()
 ```
@@ -399,8 +396,6 @@ You can configure how many events queue before flushing with `flushAt`. Setting
 
 You can also configure the flush interval with `flushIntervalSeconds` (default `30`), after which queued events are sent regardless of how many have been gathered:
 
-Kotlin
-
 ```kotlin
 import com.posthog.android.PostHogAndroidConfig
 
@@ -412,8 +407,6 @@ val config = PostHogAndroidConfig(apiKey = POSTHOG_API_KEY, host = POSTHOG_HOST)
 
 You can also manually flush the queue to start sending events immediately instead of waiting for the next batch:
 
-Kotlin
-
 ```kotlin
 import com.posthog.PostHog
 
@@ -426,8 +419,6 @@ Flushing is best-effort and asynchronous – it starts sending queued events in
 
 To reset the user's ID and anonymous ID, call `reset`. Usually you would do this right after the user logs out.
 
-Kotlin
-
 ```kotlin
 import com.posthog.PostHog
 
@@ -436,12 +427,10 @@ PostHog.reset()
 
 ## Feature Flags
 
-PostHog's [feature flags](/docs/feature-flags.md) enable you to safely deploy and roll back new features as well as target specific users and groups with them.
+PostHog's [feature flags](https://posthog.com/docs/feature-flags.md) enable you to safely deploy and roll back new features as well as target specific users and groups with them.
 
 ### Boolean feature flags
 
-Kotlin
-
 ```kotlin
 import com.posthog.PostHog
 
@@ -456,8 +445,6 @@ if (result?.enabled == true) {
 
 ### Multivariate feature flags
 
-Kotlin
-
 ```kotlin
 import com.posthog.PostHog
 
@@ -474,8 +461,6 @@ if (result?.variant == "variant-key") { // replace "variant-key" with the key of
 
 You can inspect all currently loaded feature flags with `PostHog.getAllFeatureFlags()`. It returns each flag's `key`, `enabled` state, `variant`, and `payload`, and does not send a `$feature_flag_called` event, so calling it won't affect your experiment results or flag usage analytics:
 
-Kotlin
-
 ```kotlin
 import com.posthog.PostHog
 
@@ -492,8 +477,6 @@ This means that for most screens, the feature flags are available immediately
 
 To handle this, you can use the `onFeatureFlags` callback to wait for the feature flag request to finish:
 
-Kotlin
-
 ```kotlin
 import com.posthog.PostHog
 import com.posthog.android.PostHogAndroidConfig
@@ -520,8 +503,6 @@ PostHog.reloadFeatureFlags {
 
 Feature flag values are cached. If something has changed with your user and you'd like to refetch their flag values, call:
 
-Kotlin
-
 ```kotlin
 import com.posthog.PostHog
 
@@ -532,8 +513,6 @@ PostHog.reloadFeatureFlags()
 
 To track when someone sees or interacts with a feature, use `captureFeatureView` and `captureFeatureInteraction`.
 
-Kotlin
-
 ```kotlin
 import com.posthog.PostHog
 
@@ -549,8 +528,6 @@ To have your feature flags available immediately, you can initialize PostHog wit
 
 Set `config.bootstrap` before calling `setup()` to seed identity and flag values before the first `/flags` response (requires Android SDK `3.55.0`+):
 
-Kotlin
-
 ```kotlin
 import com.posthog.PostHogBootstrapConfig
 
@@ -573,13 +550,11 @@ PostHogAndroid.setup(this, config)
 
 The feature-flags-loaded signal fires as soon as bootstrapped flags are applied, so startup logic can read them immediately. These SDKs don't support the `sessionID` bootstrap option. When person profiles are set to `never`, the SDK preserves a different anonymous identity instead of merging it into an identified bootstrap.
 
-See the [SDK bootstrapping guide](/docs/libraries/bootstrapping.md) for the cross-SDK overview.
+See the [SDK bootstrapping guide](https://posthog.com/docs/libraries/bootstrapping.md) for the cross-SDK overview.
 
 ## Experiments (A/B tests)
 
-Since [experiments](/docs/experiments/start-here.md) use feature flags, the code for running an experiment is very similar to the feature flags code:
-
-Kotlin
+Since [experiments](https://posthog.com/docs/experiments/start-here.md) use feature flags, the code for running an experiment is very similar to the feature flags code:
 
 ```kotlin
 import com.posthog.PostHog
@@ -589,18 +564,16 @@ if (PostHog.getFeatureFlag("experiment-feature-flag-key") == "variant-name") {
 }
 ```
 
-It's also possible to [run experiments without using feature flags](/docs/experiments/running-experiments-without-feature-flags.md).
+It's also possible to [run experiments without using feature flags](https://posthog.com/docs/experiments/running-experiments-without-feature-flags.md).
 
 ## Group analytics
 
-Group analytics allows you to associate the events for that person's session with a group (e.g. teams, organizations, etc.). Read the [Group Analytics](/docs/user-guides/group-analytics.md) guide for more information.
+Group analytics allows you to associate the events for that person's session with a group (e.g. teams, organizations, etc.). Read the [Group Analytics](https://posthog.com/docs/user-guides/group-analytics.md) guide for more information.
 
-> **Note:** This is a paid feature and is not available on the open-source or free cloud plan. Learn more on the [pricing page](/pricing.md).
+> **Note:** This is a paid feature and is not available on the open-source or free cloud plan. Learn more on the [pricing page](https://posthog.com/pricing.md).
 
 -   Associate the events for this session with a group
 
-Kotlin
-
 ```kotlin
 import com.posthog.PostHog
 
@@ -613,8 +586,6 @@ PostHog.group(
 
 -   Associate the events for this session with a group AND update the properties of that group
 
-Kotlin
-
 ```kotlin
 import com.posthog.PostHog
 
@@ -629,21 +600,21 @@ The `name` is a special property which is used in the PostHog UI for the name of
 
 ## Error tracking
 
-To set up error tracking in your project, see the [error tracking docs](/docs/error-tracking.md).
+To set up error tracking in your project, see the [error tracking docs](https://posthog.com/docs/error-tracking.md).
 
 ## Logs
 
-To set up [logs](/docs/logs.md) in your Android app, follow the [Android logs installation guide](/docs/logs/installation/android.md). The SDK exposes `PostHog.logger.{trace,debug,info,warn,error,fatal}` for sending structured records to PostHog Logs, with batching, offline persistence, and a rate cap built in.
+To set up [logs](https://posthog.com/docs/logs.md) in your Android app, follow the [Android logs installation guide](https://posthog.com/docs/logs/installation/android.md). The SDK exposes `PostHog.logger.{trace,debug,info,warn,error,fatal}` for sending structured records to PostHog Logs, with batching, offline persistence, and a rate cap built in.
 
 > **Minimum version:** `com.posthog:posthog-android@3.46.0` or later.
 
 ## Session replay
 
-To set up [session replay](/docs/session-replay/mobile.md) in your project, all you need to do is install the Android SDK, enable "Record user sessions" in [your project settings](https://us.posthog.com/settings/project-replay) and enable the `sessionReplay` option.
+To set up [session replay](https://posthog.com/docs/session-replay/mobile.md) in your project, all you need to do is install the Android SDK, enable "Record user sessions" in [your project settings](https://us.posthog.com/settings/project-replay) and enable the `sessionReplay` option.
 
 ## Surveys
 
-To set up surveys, follow the [additional installation instructions for Android](/docs/surveys/installation/android.md). Surveys launched with [popover presentation](/docs/surveys/creating-surveys.md#presentation) are automatically shown to users matching the [display conditions](/docs/surveys/creating-surveys.md#display-conditions) you set up.
+To set up surveys, follow the [additional installation instructions for Android](https://posthog.com/docs/surveys/installation/android.md). Surveys launched with [popover presentation](https://posthog.com/docs/surveys/creating-surveys.md#presentation) are automatically shown to users matching the [display conditions](https://posthog.com/docs/surveys/creating-surveys.md#display-conditions) you set up.
 
 ## Offline behavior
 
@@ -660,8 +631,6 @@ If you're not seeing the expected events being captured, the feature flags being
 
 You can enable debug mode by setting the `debug` option to `true` in the `PostHogAndroidConfig` object. This will enable verbose logs about the inner workings of the SDK.
 
-Kotlin
-
 ```kotlin
 val config = PostHogAndroidConfig(apiKey = POSTHOG_API_KEY, host = POSTHOG_HOST).apply {
     debug = true
@@ -673,8 +642,6 @@ val config = PostHogAndroidConfig(apiKey = POSTHOG_API_KEY, host = POSTHOG_HOST)
 
 When creating the PostHog client, pass a `PostHogAndroidConfig`. It inherits the core `PostHogConfig` options and adds Android-specific options.
 
-Kotlin
-
 ```kotlin
 import com.posthog.PersonProfiles
 import com.posthog.android.PostHogAndroidConfig
@@ -727,7 +694,7 @@ val config = PostHogAndroidConfig(
 | `flushAt` | `20` | Number of queued events that triggers a flush. |
 | `maxQueueSize` | `1000` | Maximum number of events kept across memory and disk before FIFO eviction. |
 | `maxBatchSize` | `50` | Maximum number of events sent in one batch request. |
-| `maxRetries` | `3` | Maximum retry attempts for failed requests. |
+| `maxRetries` | `3` | Maximum retry attempts for push-subscription registration failures. It does not apply to event, session recording, or log ingestion. |
 | `flushIntervalSeconds` | `30` | Maximum delay before queued data is flushed. |
 | `encryption` | `null` | Optional `PostHogEncryption` implementation for encrypting persisted queued events. |
 | `proxy` | `null` | Optional `java.net.Proxy` for PostHog API requests. |
@@ -754,18 +721,16 @@ val config = PostHogAndroidConfig(
 | --- | --- | --- |
 | `sessionReplay` | `false` | Enables session replay when project settings also allow recording. |
 | `sessionReplayConfig` | `PostHogSessionReplayConfig()` | Configures masking, screenshots, Logcat capture, sampling, and custom drawable conversion. |
-| `logs` | `PostHogLogsConfig()` | Configures [Android logs](/docs/logs/installation/android.md). |
+| `logs` | `PostHogLogsConfig()` | Configures [Android logs](https://posthog.com/docs/logs/installation/android.md). |
 | `errorTrackingConfig` | `PostHogErrorTrackingConfig()` | Configures error tracking. `autoCapture` defaults to `false`; set it to `true` to autocapture uncaught exceptions when project settings also enable error tracking. |
 | `surveys` | `false` | Internal/experimental native Android survey support. Native Android survey UI is not fully supported or documented yet. |
 | `surveysConfig` | `PostHogSurveysConfig()` | Internal/experimental survey display delegate configuration, primarily for hybrid SDKs. |
-| `bootstrap` | `null` | Seeds identity (`distinctId`, `isIdentifiedId`) and feature-flag state (`featureFlags`, `featureFlagPayloads`) before the first `/flags` response. Bootstrapped identity applies to the first session; only enabled flags are served, until the first `/flags` response replaces them. See [SDK bootstrapping](/docs/libraries/bootstrapping.md#behavior-on-mobile-sdks). |
+| `bootstrap` | `null` | Seeds identity (`distinctId`, `isIdentifiedId`) and feature-flag state (`featureFlags`, `featureFlagPayloads`) before the first `/flags` response. Bootstrapped identity applies to the first session; only enabled flags are served, until the first `/flags` response replaces them. See [SDK bootstrapping](https://posthog.com/docs/libraries/bootstrapping.md#behavior-on-mobile-sdks). |
 
 ### Event filtering with `beforeSend`
 
 Use `addBeforeSend` to redact, modify, or drop events before they are queued. Return `null` to drop an event.
 
-Kotlin
-
 ```kotlin
 config.addBeforeSend { event ->
     event.properties?.remove("password")
@@ -784,8 +749,6 @@ You can stop specific screens from being autocaptured by filtering them in your
 
 Because it's just a function, you can filter however you like – an **ignorelist** (drop the screens you name), an **allowlist** (invert the check to capture only the screens you name), or any custom rule such as a name prefix, a regex, or a check against the event's properties.
 
-Kotlin
-
 ```kotlin
 val ignoredScreens = setOf("Splash", "Debug")
 
@@ -801,7 +764,7 @@ config.addBeforeSend { event ->
 
 ## Push notifications
 
-The Android SDK can register a device for [Workflows](/docs/workflows.md) push notifications and capture when a user opens one. For setup, including automatic and manual registration, capturing opens, opting out, and identity verification, see [Push notifications](/docs/workflows/push-notifications.md).
+The Android SDK can register a device for [Workflows](https://posthog.com/docs/workflows.md) push notifications and capture when a user opens one. For setup, including automatic and manual registration, capturing opens, opting out, and identity verification, see [Push notifications](https://posthog.com/docs/workflows/push-notifications.md).
 
 ## FAQ
 
@@ -812,11 +775,3 @@ The Android SDK supports Android API 23 and newer.
 ## Do I need to declare permissions in the AndroidManifest.xml?
 
 Usually, no. The SDK declares `android.permission.INTERNET` and `android.permission.ACCESS_NETWORK_STATE`, and Android's manifest merger adds them to your app. The SDK does not declare or require an Android `Service`.
-
-### Still have questions?
-
-Ask PostHog AI
-
-### Was this page useful?
-
-HelpfulCould be better