docs(ios): add dSYM Input Files step and content_hash_mismatch troubleshooting#16165
Open
docs(ios): add dSYM Input Files step and content_hash_mismatch troubleshooting#16165
Conversation
Contributor
Deploy preview
|
Contributor
|
Vale prose linter → found 1 errors, 17 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!
|
| 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 |
| 66:4 | warning | 'symbolicate' is a possible misspelling. | PostHogBase.Spelling |
| 66:144 | warning | 'dSYMs' is a possible misspelling. | PostHogBase.Spelling |
| 118:112 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 160:14 | warning | 'uncheck' is a possible misspelling. | PostHogBase.Spelling |
| 168:15 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 184:5 | warning | 'Script fails with "error: posthog-cli not found"' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 184:31 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 184:39 | warning | Use 'CLI' instead of 'cli'. | Vale.Terms |
| 201:5 | warning | 'dSYMs' is a possible misspelling. | PostHogBase.Spelling |
| 201:5 | warning | 'dSYMs not being generated' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 207:200 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
ioannisj
approved these changes
Apr 3, 2026
| 6. In the **Input Files** section of the Run Script phase, add: | ||
|
|
||
| ``` | ||
| $(DWARF_DSYM_FOLDER_PATH)/$(DWARF_DSYM_FILE_NAME) |
Contributor
There was a problem hiding this comment.
${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}/Contents/Resources/DWARF/${EXECUTABLE_NAME}
When I tested, this worked as well. Why not look at executable's dsym alone?
|
|
||
| ### Script fails with "content_hash_mismatch" | ||
|
|
||
| This happens when the upload script runs before Xcode finishes generating the dSYM files. Add `$(DWARF_DSYM_FOLDER_PATH)/$(DWARF_DSYM_FILE_NAME)` to the **Input Files** of the Run Script build phase — this tells Xcode to complete dSYM generation before running the upload script. No newline at end of file |
Contributor
There was a problem hiding this comment.
I think that Input files just prevent the script from running until this file has changed. So not sure how correct this explanation here is?
If that's the case, then we should probably also mention checking "Based on dependency analysis" as well (which is the default when adding a new Run Script phase)
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
2 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.
What
Two small additions to the iOS dSYM upload guide:
Step 6 — Input Files: adds an explicit instruction to add
$(DWARF_DSYM_FOLDER_PATH)/$(DWARF_DSYM_FILE_NAME)to the Run Script build phase's Input Files section, so Xcode waits for dSYM generation before running the upload script.New troubleshooting entry —
content_hash_mismatch: explains why the error occurs (upload script runs before dSYM generation finishes) and how to fix it (same Input Files tip).Why
Users were hitting
content_hash_mismatcherrors on incremental builds because the upload script was running before the dSYM was fully written. The fix is documented in the CLI but wasn't covered in the iOS upload guide.