Skip to content

Acquiring an exclusive Navigator LockManager failed #936

@supersu-man

Description

@supersu-man

Bug report

  • I confirm this is a bug with Supabase, not with my own application.
  • I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

Angular throws an error saying 'Acquiring an exclusive Navigator LockManager lock immediately failed'.
This is a new angular project created with the angular version 17.
The error is not shown in my other project which is created a month ago.

To Reproduce

  1. Create a new angular project and install '@supabase/supabase-js'
  2. Create environment files and add key and url of supabase.
  3. add supabaseClient = createClient(environment.url, environment.key) to a component (app component)

Expected behavior

This error should not be thrown and should be able to use all the methods without errors.

Screenshots

Error

System information

  • OS: Windows
  • Browser: Brave v1.61.109
  • Version of supabase-js: 2.39.2
  • Version of Node.js: 20.10.0

Additional context

Could be a duplicate of this issue from gotrue-js.
Though I was able to signin using provider 'google' I wasn't able to retrieve session after I signin (throws an error saying Invalid API key) though my api keys and url are correct. I am assuming the error is with storage.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workinghas workaroundIssue has a valid workaround.retry with latestUsers should retry with latest version of the SDK.temp - locksTemporary label to group together all the lock-related issues and PRs.

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions