Repository navigation
chore(examples): move the mobile example apps to the new SDK majors - #479
Draft
turnipdabeets wants to merge 3 commits into
Draft
turnipdabeets wants to merge 3 commits into
turnipdabeets wants to merge 3 commits into
Conversation
… pins on the installed major
Collaborator
|
@turnipdabeets I'm gonna ask y'all hold your horses for these even after the SDK release while we do some prep work and figure out how we handle both new and old majors of these SDKs in the Wizard. Some programs extend existing Wizard integrations, and doing a one and done replacement of the examples might really confuse the Wizard. We're thinking of doing versioned skills, so we might take this PR and base this on other changes and/or base changes on top of this. So leave this to us to mess about and merge! |
This was referenced Nov 6, 2026
… to new majors posthog-ios 4.x ships only through SPM; posthog_flutter 6.x needs SPM, Flutter 3.41+ and iOS 15; @posthog/react-native-plugin 3.x needs RN 0.75+.
This was referenced Nov 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Important
Don't merge until posthog-android 4.0, posthog-ios 4.0 and posthog_flutter 6.0 are all published. Until then,
4.+,from: "4.0.0"and^6.0.0don't resolve and the example apps don't build. Flutter 6.0 ships after the native 4.0 releases, so this PR merges on the Flutter release day.Problem
The Android, iOS and Flutter example apps pin the current SDK majors, so they never pick up posthog-android 4.0, posthog-ios 4.0 or posthog_flutter 6.0. The source maps skill also says Flutter always uses CocoaPods, which is wrong from posthog_flutter 6.0.
Changes
Android:
posthoggoes from3.72.1to4.0.0inlibs.versions.toml, and the README install line goes from3.+to4.+.iOS (
swift): the Swift Package Manager requirement goes from up to next major from3.56.0to4.0.0.iOS (
swift-xcodegen):from: 3.64.1becomesfrom: 4.0.0inproject.ymland the README. Their comments say to stay on the project's major instead of checking for the latest release.Flutter:
posthog_flutter: ^6.0.0. The Runner projects target iOS 15.0 and macOS 11.0.Flutter tests: the platform fake in
test/mocks.darttakes theoptionsparameter that 6.0 adds toidentify,capture,captureExceptionandscreen. Without it, no test file compiles on 6.0.Flutter CocoaPods: both Podfiles are deleted, because
posthog_flutter6 is a Swift package and the app has no other plugins. The README dropspod installand asks for Xcode 26 and Flutter 3.44.2, the first release that meets the app's Dart constraint with Swift Package Manager on by default.error-tracking-upload-source-maps/description.md: the CocoaPods dSYM path is marked posthog-ios 3.x only. The Flutter line says 6.0 and later use the Swift Package Manager path, and 5.x uses CocoaPods.commandments.yaml, two rules feat(integration): rules and agent wording per capture mode #455 doesn't touch:from:the detect_package_manager requirement or the installed major'sx.0.0, matching the pbxproj rule in feat(integration): rules and agent wording per capture mode #455, instead of the latest release.beforeSendrule now covers both majors. On 6.x the callback gets the full native event and must be synchronous. Natively captured events needPosthogFlutterPlugin.addBeforeSend.The other wizard rules for each major live in #455, and the frozen 3.x and 5.x pages in #454 and #471. The XcodeGen rule sits next to a line #455 rewrites, so whichever PR merges second may need a small rebase.
Not changed:
Package.resolved(swift) andpubspec.lock(flutter) still name the old versions. Xcode andflutter pub getre-resolve them against the new requirements, and they can be refreshed after the releases.Open question with Eli (context-mill#454): example_paths now point to 4.0/6.0 apps while legacy variants' docs_urls point at 3.x/5.x snapshots.
Test plan
test/mocks.dartchange,flutter analyzeis clean and all 13 tests pass, run against thechore/v6-posthog-ios-4source in a scratch copy rather than a published 6.0.0.commandments.yamlstill loads as YAML.pnpm test, because the worktree has no installed dependencies.LLM context
Written with Claude Code (Opus 5.5) at the request of the posthog-android maintainer, from an audit of
mainagainst the 4.0 and 6.0 release notes in PostHog/posthog.com#21807, #21808 and #20924.🤖 Generated with Claude Code