Extension wallet permission errors on google chrome

[diomark]

This issue started today, and might be related to a google chrome update.

Received error when attempting to sign -

The following errors are visible in google chrome extensions screen -

I asked another user (cgi-bin) to check and he's getting the same behavior. For him the wallet is working on firefox but not on chrome.

[polarker]

@h0ngcha0 Please help us investigate!

[h0ngcha0]

Question: when you get this error, is the current active (selected) account the same as the connected account?

[diomark]

i think the error might just be as symptom (?) afterwards nothing worked in my wallet (empty balances)
btw this is under Chrome Version 133.0.6943.142 (Official Build) (64-bit)

[diomark]

chrome updated to updated to Version 134.0.6998.36 (Official Build) (64-bit) still broken - still broken. (confirmed with cgi his is also still broken)

MiniJudie is using debian/chrome 134.0.6998.35 from repo, and hers works.

[MiniJudie]

isnt that https://www.extension.ninja/blog/post/solved-permission-is-unknown-or-url-pattern-is-malformed/ ? but thats kinda old

[diomark]

Talking with HongChao and others. two seperate issues here -

1. pub key mismatch (wrong address selected, but it used to switch automatically)
2. google chrome extension storage quotas

The storage quota throws this error if you dig in the console logs (inspect) -
QuotaExceededError: Failed to execute 'setItem' on 'Storage': Setting the value of 'core:transactions' exceeded the quota.

[h0ngcha0]

Talking with HongChao and others. two seperate issues here -

1. pub key mismatch (wrong address selected, but it used to switch automatically)
2. google chrome extension storage quotas

The storage quota throws this error if you dig in the console logs (inspect) - QuotaExceededError: Failed to execute 'setItem' on 'Storage': Setting the value of 'core:transactions' exceeded the quota.

v0.9.19 is released to both chrome and firefox to address the public key mismatch issue. Please check if it is fixed, thanks 🙏