Settings Component Shows Blank Page After Successful Deployment

Develop, Build & Integrate APIs & Integrations
1

Can you please check for me.The Settings component has been successfully deployed, and the build completed successfully. However, when opening the Settings tab, it remains stuck on the loading state and then displays a blank page. The component content is not rendered.

App ID: redacted
Portal ID: redacted
Thanks.

Screenshot 2026-09-13 212420
Screenshot 2026-09-13 212420802×484 21.2 KB

2

Hey @Ethan,

Thanks for bringing this to the community! :glowing_star:

To start, are you able to check the browser console for errors, and look for a Log Traces entry with a trace ID. HubSpot surfaces a banner with a trace ID when a UI extension fails to render, per Create private apps with projects.

Also tagging in some of our Top Contributors to see if they have any tips and tricks on this!

Hey @Alex_Boissonneault, @Josh, @GRajput – Do you have any suggestions for @Ethan on this?

Thanks in advance!!

Sam, Community Manager

3

Thanks for looping me in @stassey!

Hey @Ethan, the screenshot actually tells m quite a bit. The “General” nav item and the “Powered by Shopify Sync by Hubsy” line are rendered by HubSpot’s settings shell, not by your component. So the extension is registered and discovered correctly. The failure is happening at the point HubSpot mounts your React bundle, and the error boundary is swallowing it, which is why you see a spinner and a blank frame instead of the trace-ID banner.

Based on that, here’s what you should follow to fix, in order:

  1. Remove any context.crm access. Settings pages have no record context, so context.crm.objectId (or similar) is null and throws on first render. This is the single most common cause of a blank settings page on 2025.2.
  2. Make sure every hubspot.fetch() target is listed in allowedUrls in app-hsmeta.json, then update the app in the test account (Connected apps > your app > Update). A blocked fetch rejects silently and leaves your loading state stuck. Adding the URL alone isn’t enough; the installed app has to be updated to pick up the new allowlist.
  3. Confirm platformVersion in hsproject.json is 2025.2 or 2026.03. Settings components aren’t supported on 2025.1, and the build will still succeed, it just won’t render.

To confirm which of these it is, replace your component’s return with a single <Text>hello</Text> and redeploy. If that renders, the issue is inside your component logic (point 1 or 2). If it’s still blank, it’s point 3 or a stale install, and at that stage the trace ID @stassey has mentioned is what support will need.

Happy to review your app-hsmeta.json and the console output if you want a second pair of eyes.