Skip to content

:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.

chore(mobile): request the 1.9.0 native release (#128737)

Chris Volzer81cc6b95d833
diff --git a/products/mobile/app.config.ts b/products/mobile/app.config.ts
index fa7ea7f8f0a3..be9392e3931b 100644
--- a/products/mobile/app.config.ts
+++ b/products/mobile/app.config.ts
@@ -59,7 +59,7 @@ export default ({ config, projectRoot }: ConfigContext): ExpoConfig => {
slug: 'posthog',
owner: 'posthog',
scheme,
- version: '1.8.0',
+ version: '1.9.0',
orientation: 'default',
userInterfaceStyle: 'automatic',
icon: icons.png,
diff --git a/products/mobile/docs/RELEASING.md b/products/mobile/docs/RELEASING.md
index 546da32a3f68..a873dd2c4b9b 100644
--- a/products/mobile/docs/RELEASING.md
+++ b/products/mobile/docs/RELEASING.md
@@ -102,6 +102,12 @@ This release uses the updated hosted workflow and includes the report chart, And
It submits to TestFlight and Google Play internal testing. Add the submitted builds to the existing external testing tracks separately.
Publish an OTA for the `1.8.0` runtime only after the native release receipt completes.
+Version `1.9.0` requests both native builds through `native-190`, following the last completed release, `native-180`.
+The `ota-180-20261102` request failed before claiming a release and remains historical.
+This release includes the connection recovery, offline cache, chat navigation, regional status, iPhone Duo layout and Android notification startup changes already on `master`.
+Native configuration and dependency changes require new binaries and a new runtime.
+It submits to TestFlight and Google Play internal testing; public-store promotion remains manual after testing.
+
The native receipt records the certificate fingerprint. An OTA request must match it as well as the native fingerprints; a receipt without a certificate fingerprint cannot authorize an OTA.
Rotate the key and certificate together, retain the old material securely for older runtimes, and raise the app version in a new native release before publishing updates with the new key.
diff --git a/products/mobile/releases/requests/native-190.json b/products/mobile/releases/requests/native-190.json
new file mode 100644
index 000000000000..80022175e108
--- /dev/null
+++ b/products/mobile/releases/requests/native-190.json
@@ -0,0 +1,8 @@
+{
+ "schemaVersion": 1,
+ "id": "native-190",
+ "kind": "native",
+ "runtimeVersion": "1.9.0",
+ "previousRelease": "native-180",
+ "notes": "This release includes connection recovery, offline access to recent analytics and inbox data, improved chat navigation, regional service status, iPhone Duo layouts, and Android notification startup fixes. Verify sign-in, recovery after going offline, cached reports and views, queued chats across restarts, regional status, narrow and wide layouts, and notification taps from a cold start on iOS and Android."
+}