Skip to content

ReferenceError: Can't find variable: BroadcastChannel #12936

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
maiconcarraro opened this issue May 4, 2025 · 1 comment · May be fixed by #12937
Closed

ReferenceError: Can't find variable: BroadcastChannel #12936

maiconcarraro opened this issue May 4, 2025 · 1 comment · May be fixed by #12937
Labels
bug Something isn't working invalid reproduction The issue did not have a detectable valid reproduction URL triage Unseen or unconfirmed by a maintainer yet. Provide extra information in the meantime.

Comments

@maiconcarraro
Copy link

Environment

  npmPackages:
    @auth/prisma-adapter: ^2.9.0 => 2.9.0
    next: ^15.3.1 => 15.3.1
    next-auth: 5.0.0-beta.27 => 5.0.0-beta.27
    react: ^19.1.0 => 19.1.0

The issue was captured by Sentry, the device is:

Browser: Safari 15.3
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.3 Safari/605.1.15
Device: Mac

Grouping
  system
    exception
      stack-trace
        frame
          module  chunks/node_modules/next-auth/react
          context-line  broadcastChannel.postMessage({
        frame
          module  chunks/node_modules/next-auth/react
          context-line  return new BroadcastChannel("next-auth");
      typeReferenceError

Reproduction URL

Using default

Describe the issue

Image

How to reproduce

Just call getSession on Safari 15.3 or lower

Expected behavior

Not throw

@maiconcarraro maiconcarraro added bug Something isn't working triage Unseen or unconfirmed by a maintainer yet. Provide extra information in the meantime. labels May 4, 2025
@github-actions github-actions bot closed this as completed May 4, 2025
Copy link

github-actions bot commented May 4, 2025

We could not detect a valid reproduction link. Make sure to follow the bug report template carefully.

Why was this issue closed?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need a link to a public GitHub repository. Example: (NextAuth.js example repository).

The bug template that you filled out has a section called "Reproduction URL", which is where you should provide the link to the reproduction.

  • If you did not provide a link or the link you provided is not hosted on github.com outside of the next-auth organization, we will close the issue.
  • If you provide a link to a private repository, we will close the issue.
  • If you provide a link to a repository but not in the correct section, we will close the issue.

What should I do?

Depending on the reason the issue was closed, you can do the following:

  • If you did not provide a link hosted on github.com outside of the next-auth organization, please open a new issue with a link to such a reproduction.
  • If you provided a link to a private repository, please open a new issue with a link to a public repository.
  • If you provided a link to a repository but not in the correct section, please open a new issue with a link to a reproduction in the correct section.

In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue.

My repository is private and cannot make it public

In most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:

  • Remove any code that is not related to the issue. (pages, API Routes, components, etc.)
  • Remove any dependencies that are not related to the issue.
  • Remove any third-party service that would require us to sign up for an account to reproduce the issue.
  • Remove any environment variables that are not related to the issue.
  • Remove private packages that we do not have access to.
  • If the issue is not related to a monorepo specifically, try to reproduce the issue without a complex monorepo setup

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps by opening a new issue.

I think my reproduction is good enough, why aren't you looking into it quickly?

We look into every issue and monitor open issues for new comments.

However, sometimes we might miss a few due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

@github-actions github-actions bot added the invalid reproduction The issue did not have a detectable valid reproduction URL label May 4, 2025
@github-actions github-actions bot locked and limited conversation to collaborators May 4, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working invalid reproduction The issue did not have a detectable valid reproduction URL triage Unseen or unconfirmed by a maintainer yet. Provide extra information in the meantime.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant