-
Notifications
You must be signed in to change notification settings - Fork 262
Description
Describe the bug
this error keeps popping up: navigatorLock/<@/node_modules/.vite/deps/@supabase_supabase-js.js?v=93c50648:4777:72
Apparently, error indicates that the LockManager API is being used in a context where it is not allowed. This API is often used to coordinate access to resources across multiple tabs or workers in a browser, but its usage is restricted in certain contexts, such as in iframes or environments with limited permissions.
I can't find @supabase_supabase-js.js or navigatorLock or LockManager anywhere in the code.
Link to the blitz that caused the error
Steps to reproduce
- go to Equipments page
- go to 'List view' tab
- click on 'Reserve' or in the 'Action' button
Expected behavior
just go through the equipment page and simulate reserving using mock data/input. Not freeze. Allow page to refresh or reset when returning.
Parity with Local
- I have run the project in my local machine and I could not reproduce the issue.
Screenshots
No response
Platform
Browser name = Firefox
Full version = 115.0
Major version = 115
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:109.0) Gecko/20100101 Firefox/115.0
performance.memory = undefined
Hash = c8c182a3
Additional context
I burned through over 2.5 million tokens trying to fix an error, that I am being gaslit into believing can be fixed, by finding files and code that isnt even accessible. I need my tokens or a refund back. extremely frustrating.
AND
why am i being forced to check a box on this issue page which I do not agree to..."Parity with Local
Does the issue appear only when running the WebContainer project? Or does it also appear locally?
I have run the project in my local machine and I could not reproduce the issue. *" this is phrased as a YES/NO EITHER/OR question and the only option is that I ran this locally and found no issues?????