chore: add iOS source-map fixture#2747
Merged
Merged
Conversation
This was referenced Jul 11, 2026
The source-maps upload only fires on Release builds (dSYMs + the upload phase are Release-only), so the shared scheme's Run action now uses the Release configuration — testing the flow needs no scheme fiddling. xcuserdata is per-user Xcode state; ignore it so wizard test runs leave the tree clean. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Two fixtures, one per package manager, so both wizard paths get exercised end-to-end: - ios-pod: the existing CocoaPods fixture, renamed. Exercises the hard path — .xcworkspace, pod install, Pods-owned baseConfigurationReference (the xcconfig chaining dance). - ios-spm: new fixture, same app wired via Swift Package Manager (XCRemoteSwiftPackageReference to posthog-ios). Exercises the default modern path — no workspace, no generated xcconfig, base-config slot free. Distinct bundle id (com.example.SourceMapExampleSPM) so releases and symbol sets don't collide with the pod fixture. Both ship the same pre-source-maps baseline: PostHog SDK installed and configured, Release run configuration in the shared scheme, script sandboxing off, no dSYM/upload wiring — that's the wizard's job. ios-spm verified with a headless Release simulator build. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
SourceMapExamplePods / SourceMapExampleSPM — project, target, scheme, bundle id, and app struct renamed so the fixtures are distinguishable in Xcode, PostHog releases, and symbol sets. The rendered view labels the variant. PostHog.xcconfig is gitignored in both fixtures — it holds the personal API key and must never be committed. Both verified with headless Release simulator builds. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
cat-ph
approved these changes
Jul 16, 2026
cat-ph
left a comment
cat-ph
left a comment
There was a problem hiding this comment.
looks good! just wondering, should we keep the projectToken an actual token in there?
gewenyu99
approved these changes
Jul 16, 2026
gewenyu99
left a comment
gewenyu99
left a comment
Contributor
There was a problem hiding this comment.
Noice, I have very little clue what's going on in the apps themselves but it's all test fixtures
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
3 participants
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.
Minimal examples for ios cocoa and SPM
Companion PRs