{{ message }}
Repository navigation
XCode15 and iOS 17.2 reports are not including screenshots #357
Description
the .xcresult file includes the screenshots and they are shown when opened up in Xcode. But when the screenshots weren't included in the generated HTML report.
Below is what we see when we have selected the attachment
kXCTAttachmentLegacySynthesizedEvent Download SynthesizedEvent_1_CB96CA19-EDB1-44EE-A591-2AA34822F1E7
Is there a way i can fix this ?
Activity
piofusco commentedon Jan 7, 2025
Hey there, I am also experiencing this with Xcode 15.2 and 15.4. I'm using iOS 16.0. Is this repository still being maintained? There's a lot of opened issues and little response from any of the maintainers. Curious if this issue is something a OS contributor could fix. Please advise.
tylervick commentedon Aug 11, 2026
I cannot confirm or refute this yet, and the reason is worth stating plainly: the image-attachment path has no test coverage at all.
Generating a report from the project's own fixture on
main(822129f) and counting what lands in the HTML:.mp4references.png/.jpegreferencesimg class="screenshot"The templates for screenshots exist (
HTML/screenshot.html), but nothing in the fixture suite exercises them — since Xcode 15 the sample tests produce screen recordings rather than screenshots.Tests/XCTestHTMLReportTests/CliTests.swifteven carries a commented-out image assertion with a note saying a separate fixture with screenshots enabled is needed. That was never added.So the honest position is: the screenshot rendering path could be entirely broken and every test here would still pass. Your report may well be a real bug; I have no evidence either way, which is itself the problem.
Tracked as a coverage gap in #393. A fixture that attaches real screenshots is the prerequisite for investigating this, so #393 blocks this issue rather than merely relating to it.
One detail from your screenshot that may matter: the attachment shown is
kXCTAttachmentLegacySynthesizedEvent, which is a synthesized UI event rather than a screenshot attachment. If your report contains those but nokXCTAttachmentScreenshotentries, the missing images may be an artifact of how the run captured attachments rather than of rendering. If you can share the output ofxcrun xcresulttool get --format json --legacy --path <your>.xcresultfiltered to attachment names, that would settle which of the two it is.test(fixtures): give the image rendering path its first coverage (#428)