Send Feedback button not showing when using Fillament 3.2.88 in SPA mode

[rodolfoBee]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/browser

SDK Version

8.8.0

Framework Version

Filament (Laravel framework)

Link to Sentry event

No response

SDK Setup/Reproduction Example

Sentry.init({
  dsn: "...",
  integrations: [
     Sentry.feedbackIntegration({
       colorScheme: "system",
       isEmailRequired: true,
       useSentryUser: {
       name: "name",
       email: "email",
    },
    includeReplay: true,
    triggerLabel: "Send Feedback",
    submitButtonLabel: "Send feedback",
    formTitle: "Send Feedback",
    messagePlaceholder: "What's your feedback?",
    successMessageText: "Thanks for your feedback!",
   })]
...
});

Steps to Reproduce

1. Create a simple Laravel app
2. Add filament v3.2.88 (https://filamentphp.com/docs/3.x/panels/getting-started)
3. Enable SPA mode (https://filamentphp.com/docs/3.x/panels/configuration#spa-mode)
4. Add browser SDK
5. Enable the feedback integration

Expected Result

The feedback button is shown on all pages.

Actual Result

When navigating the app in the menu created by Filament the feedback button will not show immediately. The button will only show after reloading the page.

Adding a video with the behaviour to the shadow Jira ticket as it contains PII.

┆Issue is synchronized with this Jira Improvement by Unito

[mydea]

I would assume, with pretty high confidence, that the problem here is not related to feedback, but that Sentry is not being run/initialized at all in that case. This is pretty old so not sure if possible, but could you provide logs for such a page where this was not rendered?

[mydea]

Why was this issue closed?

This issue hasn't been touched recently and no longer seems relevant.
Hence, we're closing it to maintain a clean and transparent backlog.

Please feel free to leave a comment if you think this issue should be reopened.