feat(source-map-config-issues): Implementing problem, diagnosis and troubleshooting section designs by Abdkhan14 · Pull Request #112393 · getsentry/sentry

Abdkhan14 · 2026-04-07T18:29:36Z

dev-ui link for testing: issue in dev org

A little context on the endpoint used for the diagnosis section.

GET /api/0/projects/{org}/{project}/events/{event_id}/source-map-debug-blue-thunder-edition/ — given an event, checks whether source maps can be resolved for each frame across three paths.
- Debug ID — whether the bundle has a debug ID injected and the corresponding artifacts are uploaded
- Release artifacts — whether the minified file and source map resolve correctly for the event's release/dist
- Scraping — whether Sentry attempted to fetch source maps from the deployed URL and the outcome (success, not found, disabled, timeout, etc.)

…ubleshooting section designs

cursor

Cursor Bugbot has reviewed your changes and found 3 potential issues.

Autofix Details

Bugbot Autofix prepared fixes for all 3 issues found in the latest run.

✅ Fixed: Potentially undefined sampleEventId causes invalid API request
- I added an eventId truthiness guard in useSourceMapDebugQuery and passed a safe empty-string fallback for sampleEventId so missing IDs no longer trigger .../events/undefined/... requests.
✅ Fixed: Null SDK name now enables query instead of disabling
- I restored the default behavior to disable queries when sdkName is missing and added an explicit opt-in option used only by SourceMapIssueDetails where null SDKs should still fetch.
✅ Fixed: Styled Flex wrapper replaceable with Flex props
- I removed the new styled(Flex) wrapper and replaced it with an inline Flex using paddingTop, align, and gap props.

Or push these changes by commenting:

@cursor push ce73a3a0c1

Preview (ce73a3a0c1)

diff --git a/static/app/components/events/interfaces/crashContent/exception/useSourceMapDebuggerData.tsx b/static/app/components/events/interfaces/crashContent/exception/useSourceMapDebuggerData.tsx
--- a/static/app/components/events/interfaces/crashContent/exception/useSourceMapDebuggerData.tsx
+++ b/static/app/components/events/interfaces/crashContent/exception/useSourceMapDebuggerData.tsx
@@ -49,15 +49,20 @@
   min_debug_id_sdk_version?: string | null;
 }
 
+interface UseSourceMapDebugQueryOptions {
+  shouldFetchWhenSdkNameMissing?: boolean;
+}
+
 export function useSourceMapDebugQuery(
   projectSlug: string,
   eventId: string,
-  sdkName: string | null = null
+  sdkName: string | null = null,
+  {shouldFetchWhenSdkNameMissing = false}: UseSourceMapDebugQueryOptions = {}
 ) {
   const organization = useOrganization({allowNull: true});
   const isSdkThatShouldShowSourceMapsDebugger = sdkName
     ? sdkName.startsWith('sentry.javascript.')
-    : true;
+    : shouldFetchWhenSdkNameMissing;
   return useApiQuery<SourceMapDebugBlueThunderResponse>(
     [
       getApiUrl(
@@ -72,7 +77,10 @@
       ),
     ],
     {
-      enabled: isSdkThatShouldShowSourceMapsDebugger && organization !== null,
+      enabled:
+        isSdkThatShouldShowSourceMapsDebugger &&
+        organization !== null &&
+        Boolean(eventId),
       staleTime: Infinity,
       retry: false,
       refetchOnWindowFocus: false,

diff --git a/static/app/views/issueDetails/configurationIssues/sourceMapIssues/sourceMapIssueDetails.tsx b/static/app/views/issueDetails/configurationIssues/sourceMapIssues/sourceMapIssueDetails.tsx
--- a/static/app/views/issueDetails/configurationIssues/sourceMapIssues/sourceMapIssueDetails.tsx
+++ b/static/app/views/issueDetails/configurationIssues/sourceMapIssues/sourceMapIssueDetails.tsx
@@ -17,8 +17,9 @@
 export function SourceMapIssueDetails({event, project}: SourceMapIssueDetailsProps) {
   const sourceMapQuery = useSourceMapDebugQuery(
     project.slug,
-    event.occurrence?.evidenceData?.sampleEventId,
-    event.sdk?.name ?? null
+    event.occurrence?.evidenceData?.sampleEventId ?? '',
+    event.sdk?.name ?? null,
+    {shouldFetchWhenSdkNameMissing: true}
   );
 
   return (

diff --git a/static/app/views/issueDetails/configurationIssues/sourceMapIssues/troubleshootingSection.tsx b/static/app/views/issueDetails/configurationIssues/sourceMapIssues/troubleshootingSection.tsx
--- a/static/app/views/issueDetails/configurationIssues/sourceMapIssues/troubleshootingSection.tsx
+++ b/static/app/views/issueDetails/configurationIssues/sourceMapIssues/troubleshootingSection.tsx
@@ -1,5 +1,3 @@
-import styled from '@emotion/styled';
-
 import {LinkButton} from '@sentry/scraps/button';
 import {InlineCode} from '@sentry/scraps/code';
 import {Disclosure} from '@sentry/scraps/disclosure';
@@ -121,22 +119,16 @@
             </Text>
           </Disclosure.Content>
         </Disclosure>
-        <FooterRow>
-          <Text variant="muted">{t('Not what you\u2019re looking for?')}</Text>
+        <Flex paddingTop="sm" align="center" gap="sm">
+          <Text variant="muted">{t('Not what you’re looking for?')}</Text>
           <ExternalLink href="https://docs.sentry.io/platforms/javascript/sourcemaps/troubleshooting_js/">
             <Flex align="center" gap="xs">
               <IconDocs size="xs" />
               {t('Read all documentation')}
             </Flex>
           </ExternalLink>
-        </FooterRow>
+        </Flex>
       </Stack>
     </Stack>
   );
 }
-
-const FooterRow = styled(Flex)`
-  padding-top: ${p => p.theme.space.sm};
-  align-items: center;
-  gap: ${p => p.theme.space.sm};
-`;

_{This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.}

scttcper · 2026-04-07T23:05:34Z

+  if (group.issueType === IssueType.SOURCEMAP_CONFIGURATION) {
+    return <SourceMapIssueDetails group={group} event={event} project={project} />;
+  }


are you sure we won't want anything from the existing experience?

@scttcper valid concern, in this iteration, the designs are deliberately made different to create a separation from issues representing customer data

That said, the issue type config is still fully registered, so anything from the existing experience (graph, activity, linked issues, sidebar) can be opted back in incrementally if needed.

scttcper · 2026-04-08T17:29:21Z

+  if (!data) {
+    return null;
+  }


don't think we need this if its not loading and not error

Oh I have receipts from ts check failures: https://github.com/getsentry/sentry/actions/runs/24187324827/job/70595246122?pr=112393

It would've worked for isPending check instead. Keeping the guard added a quick message for the no data case

scttcper · 2026-04-08T17:29:42Z

+      message ?? (
+        <Text>
+          {t(
+            'Source maps appear to be configured but Sentry could not pinpoint the exact issue.'
+          )}
+        </Text>
+      )


which would remove the need for this fallback

evanpurkhiser · 2026-04-08T17:37:31Z

+      <Text size="lg" bold>
+        {t('Troubleshooting suggestions')}
+      </Text>


should this be a header actually?

Yeah ^, pushed the change

evanpurkhiser · 2026-04-08T17:39:13Z

+            <Text>
+              {t(
+                'When running JavaScript build tools (like webpack, Vite, ...) in development-mode/watch-mode, the generated code is sometimes incompatible with our source map uploading processes.'
+              )}
+              <br />
+              <br />
+              {t(
+                'We recommend, especially when testing locally, to run a production build to verify your source maps uploading setup.'
+              )}
+            </Text>


Should we use Prose here (to avoid the <br />)

TIL, pushed the change ^

evanpurkhiser · 2026-04-08T17:44:59Z

   * Configuration for the issue-level information header
   */
  header: {
+    // Controls the "X in this issue" event navigation row (First/Latest/Recommended)


Suggested change

// Controls the "X in this issue" event navigation row (First/Latest/Recommended)

/**

* Controls the "X in this issue" event navigation row.

*/

Let's use a docstring here so we get this documentation in the LSP

Though it looks like some of the other ones are wrong also lol

Updated all three in the file ^

evanpurkhiser · 2026-04-08T18:31:00Z

+}
+
+interface DiagnosisSectionProps {
+  sourceMapQuery: ReturnType<typeof useSourceMapDebugQuery>;


didn't we export the type?

Yeah updated this ^

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 0955fab. Configure here.}

…roubleshooting section designs (#112393) dev-ui link for testing: [issue in dev org](https://instrument-gc.dev.getsentry.net:7999/issues/7389912885/?project=4511172452286464&query=&referrer=issue-stream) A little context on the endpoint used for the diagnosis section. - `GET /api/0/projects/{org}/{project}/events/{event_id}/source-map-debug-blue-thunder-edition/` — given an event, checks whether source maps can be resolved for each frame across three paths. - - Debug ID — whether the bundle has a debug ID injected and the corresponding artifacts are uploaded - - Release artifacts — whether the minified file and source map resolve correctly for the event's release/dist - - Scraping — whether Sentry attempted to fetch source maps from the deployed URL and the outcome (success, not found, disabled, timeout, etc.) <img width="1185" height="825" alt="Screenshot 2026-04-08 at 12 21 20 AM" src="https://github.com/user-attachments/assets/9b41cf59-16c8-40ff-babf-7e36d9893826" /> --------- Co-authored-by: Abdullah Khan <abdullahkhan@PG9Y57YDXQ.local>

Abdullah Khan added 4 commits April 7, 2026 16:48

feat(source-map-config-issues): Implementinproblem, diagnosis and tro…

5577f65

…ubleshooting section designs

feat(source-map-config-issues): Iterating

764d2b3

feat(source-map-config-issues): Iterating

8b5e24a

feat(source-map-config-issues): Iterating

b43a101

Abdkhan14 requested review from a team as code owners April 7, 2026 18:29

github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Apr 7, 2026

sentry bot reviewed Apr 7, 2026

View reviewed changes

Comment thread static/app/views/issueDetails/configurationIssues/sourceMapIssues/sourceMapIssueDetails.tsx

cursor bot reviewed Apr 7, 2026

View reviewed changes

Abdkhan14 marked this pull request as draft April 7, 2026 18:57

scttcper reviewed Apr 7, 2026

View reviewed changes

feat(source-map-issues): Addressing pr suggestions

cacc0da

vercel bot deployed to Preview April 8, 2026 07:33 View deployment

Abdkhan14 requested a review from scttcper April 8, 2026 07:52

Merge branch 'master' into abdk/config-issues-ui-v1

e989b3b

vercel bot deployed to Preview April 8, 2026 08:36 View deployment

Abdkhan14 marked this pull request as ready for review April 8, 2026 16:33

sentry bot reviewed Apr 8, 2026

View reviewed changes

Comment thread static/app/views/issueDetails/configurationIssues/sourceMapIssues/diagnosisSection.tsx

feat(source-map-issues): Addressing pr suggestions

b8fd217

vercel bot deployed to Preview April 8, 2026 16:46 View deployment

sentry bot reviewed Apr 8, 2026

View reviewed changes

Comment thread static/app/views/issueDetails/configurationIssues/sourceMapIssues/diagnosisSection.tsx Outdated

cursor bot reviewed Apr 8, 2026

View reviewed changes

Comment thread static/app/views/issueDetails/configurationIssues/sourceMapIssues/diagnosisSection.tsx Outdated

feat(source-map-issues): Addressing pr suggestions

311092a

vercel bot deployed to Preview April 8, 2026 17:02 View deployment

cursor bot reviewed Apr 8, 2026

View reviewed changes

Comment thread static/app/views/issueDetails/configurationIssues/sourceMapIssues/sourceMapIssueDetails.tsx

Merge branch 'master' into abdk/config-issues-ui-v1

e9936d4

vercel bot deployed to Preview April 8, 2026 17:13 View deployment

sentry bot reviewed Apr 8, 2026

View reviewed changes

Comment thread static/app/components/events/interfaces/crashContent/exception/useSourceMapDebuggerData.tsx

Abdkhan14 changed the title ~~feat(source-map-config-issues): Implementinproblem, diagnosis and troubleshooting section designs~~ feat(source-map-config-issues): Implementing problem, diagnosis and troubleshooting section designs Apr 8, 2026

scttcper reviewed Apr 8, 2026

View reviewed changes

scttcper approved these changes Apr 8, 2026

View reviewed changes

evanpurkhiser reviewed Apr 8, 2026

View reviewed changes

evanpurkhiser approved these changes Apr 8, 2026

View reviewed changes

feat(source-map-issues): Addressing pr suggestions

0955fab

vercel bot deployed to Preview April 9, 2026 11:18 View deployment

cursor bot reviewed Apr 9, 2026

View reviewed changes

Comment thread static/app/components/events/interfaces/crashContent/exception/useSourceMapDebuggerData.tsx

feat(source-map-issues): Addressing pr suggestions

81dfb8d

vercel bot deployed to Preview April 9, 2026 11:51 View deployment

Abdkhan14 merged commit 629be90 into master Apr 9, 2026
65 checks passed

Abdkhan14 deleted the abdk/config-issues-ui-v1 branch April 9, 2026 17:02

Uh oh!

Conversation

Abdkhan14 commented Apr 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

cursor bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

evanpurkhiser Apr 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

cursor bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Abdkhan14 commented Apr 7, 2026 •

edited

Loading

cursor bot left a comment •

edited

Loading

evanpurkhiser Apr 8, 2026 •

edited

Loading