feat: error tracking upload source maps#162
Conversation
127ce0a to
a49c457
Compare
gewenyu99
left a comment
There was a problem hiding this comment.
If it works it works my dude.
All I'll ask is you:
- run this on a few production projects you find on GitHub
- Run some analysis on the full wizard logs. Tell Claude or Codex to look for errors, wasted turns, inefficiencies
- Fix the prompts.
If you've done this, we can ship as is. If not, you'll find some interesting things to fix for sure ;)
| description: Upload dSYM debug symbols to PostHog Error Tracking for iOS | ||
| tags: [ios, swift] | ||
| docs_urls: | ||
| - https://posthog.com/docs/error-tracking/upload-source-maps/ios.md |
There was a problem hiding this comment.
Let'sss go.
A very clean matrix. If you're not doing CI yet, let's remove
` - https://posthog.com/docs/error-tracking/upload-source-maps/github-actions.md
for now.
It's just gonna be noise and I don't wanna see the agent being keen and acting on it without explicit direction
There was a problem hiding this comment.
Tested on https://github.com/cryptly-dev/cryptly/tree/main/frontend. WENT FLAWLESS. No stops, no errors, nothing to optimize. True 1 shot
There was a problem hiding this comment.
Alright now tested on backend. WORKED FLAWLESSLY!!!!!!
No CI flow yet, so the github-actions.md reference is just noise. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Wizard PR - PostHog/wizard#475
Workbench PR - PostHog/wizard-workbench#1685
Adds an
error-tracking-upload-source-mapsskill.