Unable to connect dApp to Polkadot.js Extension accounts due to error `Resource::kQuotaBytes quota exceeded`

[ltfschoen]

I'm using the latest:

• polkadot.js extension 0.60.1
• Brave browser Brave 1.79.126 (Official Build) (arm64) Chromium: 137.0.7151.119

I've developed a desktop-based OpenGov governance dApp where instead of the security concern of hardcoding a mnemonic in a .env file i run a server that has a frontend where I click to connect an account and it opens the Polkadot.js Extension and asks which accounts to connect, but even if I select an account as shown below when using the latest Brave browser, it is not possible to click the button <div class="children">Connect 1 account(s)</div>, whereas in Chrome browser it is possible to click it.

Note: In the screenshot I haven't shown the account that I selected, it's greyed out.

It appears to be caused in ./extension/packages/extension-ui/src/Popup/Authorize/Request.tsx where "Connect {{total}} account(s)" button is implemented.
I tried turning of Brave shields incase the button click handler was blocked by security features, and turning off fingerprinting incase that was blocking event handlers and propagation, but that didn't appear to work.

Is it possible to get OpenGov funding for the product manager of this extension to use Browserstack or similar equivalent to reduce the likelihood of these cross-browser compatibility issues arising, because it's a major painpoint for long-term users and would be a major deterrent for any new users that want to use this product in their browser of choice, rather than having to sacrifice their privacy or by using other wallet extensions. Imagine if Metamask didn't work in Brave due to a similar issue and it only worked in Chrome.

[brenzi]

same issue here. While I do see my accounts to select, The "connect N accounts" button is dead

[Juanma0x]

I can reproduce the issue on Chrome 137.0.7151.120, though the behavior varies slightly depending on the site you're trying to connect to:

• Polkadot-JS UI: The "Connect n account(s)" works, but the accounts that were not added previously do not show up on Polkadot-JS UI. The selected accounts are not kept selected in "Accounts connected to polkadot.js.org". Behaviour similar to the one described by issue Missing checkmark for connected account in extension #1566.
• Other dApps (e.g., the Staking Dashboard): The "Connect n account(s)" button is not responsive.

I couldn't replicate it on Firefox (Polkadot extension is v0.58.5).

[ap211unitech]

This works for me on the Staking Dashboard as well. I noticed the issue with the list of connected accounts, which is why I created the issue for it. Everything else looks fine to me—it’s consistent across all websites I checked.

[Juanma0x]

Adding some additional details in case they help troubleshoot the issue:

• I have 29 accounts in the Polkadot extension.
• When the button becomes unresponsive, the browser console shows the following error:
  Error: Resource::kQuotaBytes quota exceeded at onPortMessageHandler (extension.js:2:1108503)
• The issue persists even in Incognito mode.
• The behavior is now the same across all dApps, including Polkadot-JS UI: the connect button is unresponsive.
• Polkadot{.js} extension version: 0.60.1
• Chrome version: 138.0.7204.50 (Official Build) (arm64)

Short video below:

Monosnap.screencast.2025-06-26.10-40-02.mp4

[brenzi]

in my case the setup is

• Brave 1.79.126 (Official Build) (64-bit) Chromium: 137.0.7151.119
• ubuntu 22.04
  I uninstalled the extension entirely and added it again. same issue

[ltfschoen]

For context, I'm trying to connect with >100 accounts. In the popup console I also get the same error Uncaught (in promise) Error: Resource::kQuotaBytes quota exceeded whenever I click the Connect 1 account(s) button, which as I previously stated doesn't work

[ltfschoen]

@brenzi @Juanma0x I've summarised my findings in this post #1564 (comment) that mentions a workaround for users to avoid encountering the Resource::kQuotaBytes quota exceeded error that appears to be caused due to a limit on the total amount of authorisations that have been granted to accounts to access dApps

I've also created a PR into Polkadot.js documentation to include the workaround in its FAQ here

I also even found today when I was developing a dApp using https://localhost:3000 that after first setting the list of accounts granted access to it in the popup, it wouldn't let me later update that list of accounts granted access to it in Manage Website Access section, instead I had to click the icon to delete that dApp from the Manage Website Access section and then reload the dApp so the popup would appear again so I could grant permissions from scratch again.