Update stale images: platforms/apple/common/tracing/instrumentation/swiftui-instrumentation (1 screenshot)

Open Beginner friendly
#18,099 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Domain
documentation

Research direction

Open the docs page and inspect platforms/apple/common/tracing/instrumentation/swiftui-instrumentation.mdx, including the adjacent img/ folder, to identify the referenced screenshot. Compare it with the current Sentry UI, recapture and replace the one stale image, and verify its alt text remains accurate. Done means the page shows the current image and the changes are ready in a PR.

Written by the indexing model from the issue text.

Description

docs-screenshots Playwright stale-image

Stale Images: platforms/apple/common/tracing/instrumentation/swiftui-instrumentation

Docs page: https://docs.sentry.io/platforms/apple/common/tracing/instrumentation/swiftui-instrumentation/
Source file: docs/platforms/apple/common/tracing/instrumentation/swiftui-instrumentation.mdx
Stale screenshots: 1
Stale Arcades: 0
Priority: medium

What to do
  1. Open the docs page and compare each screenshot against the current Sentry UI
  2. For screenshots: recapture from the current UI and replace the image file
  3. For Arcades: re-record the interactive walkthrough and update the embed URL
  4. Ensure alt text is still accurate for any replaced images
  5. Commit and open a PR
Notes
  • This issue was auto-generated by the screenshot pipeline
  • See the source MDX file for all image references
  • Images are stored in the img/ folder next to the MDX file
Dominant language
MDX
Stars
446
Forks
1.7k
Avg merge
1d 21h
Merged PRs (30d)
312

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/sentry-docs

All issues in getsentry/sentry-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.