Skip to content

docs(error-tracking): document --force flag and re-upload behavior for dSYM uploads#16185

Open
inkeep[bot] wants to merge 2 commits intomasterfrom
docs-writer-ai-update-2026-04-06T14-37-37-095Z-oe7fyg
Open

docs(error-tracking): document --force flag and re-upload behavior for dSYM uploads#16185
inkeep[bot] wants to merge 2 commits intomasterfrom
docs-writer-ai-update-2026-04-06T14-37-37-095Z-oe7fyg

Conversation

@inkeep
Copy link
Copy Markdown
Contributor

@inkeep inkeep bot commented Apr 6, 2026

Summary

Documents the new --force flag and re-upload behavior changes introduced in PostHog/posthog#53325.

Changes

iOS dSYM upload docs (contents/docs/error-tracking/upload-source-maps/ios.mdx)

  • Added note explaining that POSTHOG_INCLUDE_SOURCE=1 automatically implies --force, allowing users to upgrade from source-less to source-included uploads without issues
  • Added troubleshooting entry for "Symbol re-uploads are silently skipped" explaining:
    • Default behavior now silently skips re-uploads when content hash differs (prevents accidental overwrites)
    • How to use --force flag to explicitly overwrite existing symbol sets
    • That POSTHOG_INCLUDE_SOURCE=1 automatically forces overwrites

CLI upload snippet (contents/docs/error-tracking/_snippets/cli/upload.mdx)

  • Added paragraph explaining the silent skip behavior for source map re-uploads with different content

Context

The original PR fixed several issues with Apple dSYM symbolication:

  1. Fixed wrong architecture selection from fat (universal) dSYMs
  2. Fixed unstable source bundle hashes causing spurious content_hash_mismatch errors
  3. Fixed hash instability from fat binaries

The behavioral change documented here is that the server now silently skips changed-content re-uploads instead of returning an error. Users can use --force (dSYM uploads only) to explicitly overwrite when needed.


This PR was created by the Inkeep Content Writer agent, which is maintained by the Docs and Wizard team. Please reach out on Slack for help if needed.

@inkeep inkeep bot requested a review from hpouillot April 6, 2026 14:40
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 6, 2026

Hey @hpouillot! This docs PR was generated for you by an agent. You're responsible for reviewing and merging it into production.

  1. Review and approve the PR
  2. Merge the PR
    a. Check the preview env and CI build and merge it yourself
    b. Enable auto-merge if you're confident in the changes

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 6, 2026

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview Apr 06, 2026 02:49PM

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 6, 2026

Vale prose linter → found 0 errors, 18 warnings, 0 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/docs/error-tracking/_snippets/cli/upload.mdx — 0 errors, 1 warnings, 0 suggestions
Line Severity Message Rule
8:62 warning 'sourcemaps' is a possible misspelling. PostHogBase.Spelling
contents/docs/error-tracking/upload-source-maps/ios.mdx — 0 errors, 17 warnings, 0 suggestions
Line Severity Message Rule
2:15 warning 'dSYMs' is a possible misspelling. PostHogBase.Spelling
12:246 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
12:252 warning 'tracking's' is a possible misspelling. PostHogBase.Spelling
32:53 warning 'dSYMs' is a possible misspelling. PostHogBase.Spelling
49:30 warning 'Sandboxing' is a possible misspelling. PostHogBase.Spelling
51:48 warning 'Sandboxing' is a possible misspelling. PostHogBase.Spelling
56:18 warning 'Sandboxing' is a possible misspelling. PostHogBase.Spelling
65:4 warning 'symbolicate' is a possible misspelling. PostHogBase.Spelling
65:144 warning 'dSYMs' is a possible misspelling. PostHogBase.Spelling
108:112 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
152:11 warning 'uncheck' is a possible misspelling. PostHogBase.Spelling
160:15 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
176:5 warning 'Script fails with "error: posthog-cli not found"' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
176:31 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
176:39 warning Use 'CLI' instead of 'cli'. Vale.Terms
193:5 warning 'dSYMs not being generated' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
193:5 warning 'dSYMs' is a possible misspelling. PostHogBase.Spelling

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants