Skip to content

docs(ios): add dSYM Input Files step and content_hash_mismatch troubleshooting #16165

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hpouillot wants to merge 2 commits into
base: master
Choose a base branch
from
+13 −1
Open

docs(ios): add dSYM Input Files step and content_hash_mismatch troubleshooting #16165

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
da92885
docs(ios): add dSYM input files step and content_hash_mismatch troubl…
hpouillot Apr 3, 2026
d6664d6
docs(ios): move input files step after script example
hpouillot Apr 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion contents/docs/error-tracking/upload-source-maps/ios.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,6 +85,14 @@ ${PODS_ROOT}/PostHog/build-tools/upload-symbols.sh

</MultiLanguage>

6. In the **Input Files** section of the Run Script phase, add:

```
$(DWARF_DSYM_FOLDER_PATH)/$(DWARF_DSYM_FILE_NAME)
Copy link
Copy Markdown
Contributor

@ioannisj ioannisj Apr 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

${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?

```

This ensures the upload script runs after dSYM generation is complete.

</Step>

<Step title="Optional: Include source code context" badge="optional">
Expand Down Expand Up @@ -192,4 +200,8 @@ Ensure `ENABLE_USER_SCRIPT_SANDBOXING` is set to `NO` in your build settings.

### dSYMs not being generated

Verify that `DEBUG_INFORMATION_FORMAT` is set to **DWARF with dSYM File** for the configuration you're building (Debug or Release).
Verify that `DEBUG_INFORMATION_FORMAT` is set to **DWARF with dSYM File** for the configuration you're building (Debug or Release).

### 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.
Copy link
Copy Markdown
Contributor

@ioannisj ioannisj Apr 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)

Image

Loading