Skip to content

Stack trace Display dropdown selections (Raw Stack Trace, Unsymbolicated) no longer persist after new stack trace component rollout #114140

@InterstellarStella

Description

@InterstellarStella

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

  • Open any issue in the issue details view (e.g. https://.sentry.io/issues//).
  • Click the Display dropdown above the stack trace and toggle on Raw Stack Trace (or, on a native/JS project, Unsymbolicated).
  • Refresh the page, navigate to a different issue in the same project, or come back to the same issue from the issue stream.

Expected Result

The previously selected Raw Stack Trace / Unsymbolicated options should still be applied, the same as before the new stack trace component rollout. The legacy implementation persisted these per org/project to localStorage under the key issue-details-stracktrace-display-<org-slug>-<project-slug>, so a user who preferred raw output didn't have to re-enable it on every event.

Actual Result

Both Raw Stack Trace and Unsymbolicated reset to their defaults on every page refresh and on navigation between issues. The new view-state provider holds the values in plain React state, so nothing is written back to localStorage (or anywhere else).

This regression was introduced when issue details switched to the new component shipped in #109428 (merged 2026-03-24), and rolled forward to the stack trace preview in #111592 and shared issues in #111686.

Note: in the legacy component, Newest/Oldest sort and Most Relevant/Full Stack Trace view were also non-persistent, so this report is specifically about Raw Stack Trace and Unsymbolicated/Minified, which previously did persist.

Screenshot of the affected dropdown:
Image

Product Area

Issues

Link

No response

DSN

No response

Version

No response

Metadata

Metadata

Assignees

No fields configured for issues without a type.

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions