Secondary hub does not send useragent and breadcrumbs

• Review the documentation: https://docs.sentry.io/
• Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
• Use the latest release: https://github.com/getsentry/sentry-javascript/releases

Package + Version

• @sentry/browser

Version:

5.18.0

Description

Main angular application + angular widgets app and there are no breadcrumbs and useragent info for widgets app errors.

Main app sentry is inited like this

const integrations: any[] = [
  // ...
  new Sentry.Integrations.Breadcrumbs({ console: false }),
  new Sentry.Integrations.UserAgent(),
];

const client = new BrowserClient({
  enabled: this.enabled,
  dsn: sentryConfig.dsn,
  release,
  defaultIntegrations: false,
  integrations: () => integrations,
  beforeSend: this.beforeSend,
});

this.hub = new Hub(client);

makeMain(this.hub);

same for the widgets app, but without makeMain call and global integrations (GlobalHandlers and CaptureConsole).

We have breadcrumbs/useragent info for main app errors, but not for widgets app. After more debugging it looks like useragent is only sent when makeMain was called for secondary app (widgets). But as i understand there should be only one main hub on page, so how should we solve this and have breadcrumbs/useragent for each app on page?

[BenBach]

Also having the same issue. Using micro frontends with Sentry is currently very difficult.

[oleksandr-yefremov]

Still see this issue in

"@sentry/browser": "6.0.3",
"@sentry/tracing": "6.0.3",

So did this fix make it to v6 or not? I am struggling with Sentry for couple of days now and find it really frustrating that documentation says “all good, you can use Hub with Client for modular reporting”, but then it does not work at all and I have to dig into issues on github to find out that I have to call makeMain (not even mentioned in documentation). But then it only works for reported issues, not uncaught exceptions.
This ticket is open without milestone or update. Current ticket has milestone v6 which was not achieved and again no update. And there are many other issues which are hanging high and dry.
I can understand that your architecture was not meant for this use case, but the issues are open for more than a year and it’s time to put some commitment and announcement. If you are not gonna fix it, my team will consider moving to another error reporting tool, because Sentry just does not work in non-SPA case.