Repository navigation
docs: sort the Flutter 6.0.0 migration guide by when you make each change - #726
Conversation
…ange Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
PostHog Review · Standard · reviewed f17442f: 1 Consider.
See this review and its findings in PostHog Review. Comment @posthog review --deep for a Deep review. A Deep review takes longer and looks deeper than a Standard review.
posthog-flutter Compliance ReportDate: 2026-11-13T23:30:01.815312+00:00 ✅ All Tests Passed!232/232 tests passed Capture_V1 Tests✅ 105/105 tests passed View Details
Capture_Ai_V1 Tests✅ 110/110 tests passed View Details
Feature_Flags Tests✅ 17/17 tests passed View Details
|
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The posthog.com Flutter SDK page redirects to this reference once 6.0.0 ships, so its setup, how-to, and product sections now live in docs/getting-started.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit efbeb50)
This reverts commit 5a477a6.
… other page has Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
This conflicts with #637 now, in one spot: -see [Upgrading to capture v1 SDKs](https://posthog.com/docs/libraries/capture-v1).
+see [Upgrading to capture v1 SDKs](https://posthog.com/docs/api/capture-v1).posthog.com#21385 now publishes the page at This PR needs to land with posthog-ios#1061 and posthog-android#973. Those PRs rename the headings that #637's MIGRATION.md links to today ( |
|
One more change to bring across when you merge: a59f3ac on #637 corrects the rollback list (your "Plan a rollback" section, line ~710). I tested this on the iOS simulator and Android emulator by installing 5.60.2 over 6.0 with events queued offline: -- **AI events.** AI events queued by 6.0.0 in their own queue are never sent.
+- **AI events.** AI events queued by 6.0.0 in their own queue aren't sent by 5.x.x. They stay on the device, and 6.x.x sends them after you update again.
+- **Registered options.** Options registered with `registerOptions()` don't apply to events 5.x.x captures. They're kept, and apply again after you update to 6.x.x.The personless and |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> # Conflicts: # posthog_flutter/MIGRATION.md
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…es and semicolons Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
One more to bring across when you resolve the conflict: Flutter 3.50.0 stable (11 November) ships flutter/flutter#184590, so add-to-app modules can upgrade now. e1178f8 on #637 updates the old paragraph. A Flutter 3.50 module ( -- [ ] You embed Flutter as an iOS or macOS add-to-app module → [Use Swift Package Manager](#use-swift-package-manager)
+- [ ] You embed Flutter in an iOS app as an add-to-app module → use Flutter 3.50.0 or later, see [Use Swift Package Manager](#use-swift-package-manager)-Add-to-app modules on iOS and macOS can't upgrade yet:
-
-- **The failure.** `flutter build swift-package` still installs a Flutter module's plugins with CocoaPods on current stable releases. ...
-- **The fix in Flutter.** Flutter fixed this in [flutter/flutter#184590](...), which isn't in a stable release yet. ...
+Add-to-app modules (`flutter create -t module`) on iOS need Flutter 3.50.0 or later:
+
+- **On Flutter 3.50.0 or later.** Build the module with `flutter build swift-package`.
+- **On earlier Flutter versions.** `flutter build swift-package` installs a module's plugins with CocoaPods and stops with `Unable to find a specification for 'posthog_flutter' depended upon by 'FlutterPluginRegistrant'`, since posthog_flutter has no podspec ([flutter/flutter#184590](https://github.com/flutter/flutter/issues/184590)). Stay on posthog_flutter 5.x.x, or use the other route.
- **The other route.** (unchanged) |
Keeps this branch's restructured MIGRATION.md and changeset, and carries over what changed on #637 since the last merge: - #730: a registered process_person_profile no longer applies to identity events, so "Fix identity calls" becomes "Check registered person processing" and the identify example goes away - #729: Android build fails instead of crashing past posthog-android 4.x - e1178f8: iOS add-to-app modules work on Flutter 3.50.0 - 862cdd3: capture v1 link points at /docs/api/capture-v1 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Resolved the conflicts with #637 in a444b00, keeping this branch's structure and style. Carried over from #637: #730 (a registered |
- Intro: only analytics and AI events move to capture v1; replay, logs, flags and web keep their endpoints - Follow ups: say why they can wait (6.x.x still accepts the old names) - Redirects: iOS, macOS and Android follow the same same-origin 307/308 rule; in 5.x.x they followed redirects to any host - Native guide links point at #prepare-your-proxy and the native long-ID sections, which now exist there - Send AI events: $ai_* events sent with capture still arrive, so the move to captureAi stays a follow up - Checklist items for the six sections that had none (flag values, batch sizes, timestamps and IDs, queued events, reachability, rollback) - Regenerate references/posthog-flutter-migration.md Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Uh oh!
There was an error while loading. Please reload this page.