Solved Chrome Web Store Blocked (Snapshot 2549.3)

darrenlschultz

Following installation today of the latest Snapshot (2549.3, released today [Jan. 14, 2022]), I am unable to access the Chrome Web Store (or any page therein). Specifically, a page loads indicating that the Chrome subdomain has been “blocked,” and that it has been so blocked “by Vivaldi,” followed by this:

ERR_BLOCKED_BY_CLIENT

Here is a screenshot of the same:

Screenshot - 1_14_2022 , 2_31_50 PM.png

Any idea as to how to resolve this? Thank you!

pafflick

Here it is: Fix for the extension store – Vivaldi Browser snapshot 2553.3

Pathduck

@darrenlschultz Hello and Welcome to the Vivaldi Community

It's better to write about these things in the Snapshot release thread, where it's already been posted.
https://forum.vivaldi.net/topic/70906/a-large-round-of-fixes-and-a-double-chromium-bump-vivaldi-browser-snapshot-2549-3

It IS a Snapshot after all, so (major) bugs will happen. I'm sure they're aware of this and a fix will come, maybe have to wait over the weekend.

darrenlschultz

@pathduck Thank you, both for the welcome and the information. I will note your suggested protocol for use in future posts. Thank you for directing me to the relevant post(s) (by @Hadden89 and you) in the relevant Snapshot release thread. I will follow that thread for updates and watch for the release of the next Snapshot.

Just to clarify “best practices” for reporting a bug (or other unexpected behavior) such as this — and I assume from your reply that this is the case, but if I may ask: is a single post in the Snapshot release thread (i.e., a reply to the relevant Snapshot release “topic”) — alongside and just another in the mass of all other replies, some or most of which may consist entirely of irrelevant praise for or dislike of some new functionality, or totally irrelevant rants/raves/inside jokes — the proper or best means of promptly bringing to the attention of the Vivaldi developers an apparent bug as fundamental and disruptive as the total inability to access the Chrome web store?

As your reply implies, the bug fix will only come once the developers push it out — an event which as you say may not occur before the weekend, and which (I assume) can only occur after the developers are first made aware of the bug, and then determine its cause, and then fashion a remedy for it, and then deem it possible and prudent and proper to release a new Snapshot to fix it. Given that reality, I simply wonder whether the proper place for such a pressing bulletin is smack in the middle of garden-variety discussion about the relevant Snapshot — as non-urgent and perhaps unimportant as some or most of such discussion might generally consist.

I do not pose this question or offer these thoughts with any intention to convey sarcasm or insolence, but rather with a genuine and earnest hunger to learn from those (such as yourself) whose experience and knowledge in this area far surpasses that which I — a virtual novice — possess. In any event, I thank you for your time and consideration of my question, thanks again for your reply, and I will be grateful and appreciative of any further thoughts or responses you might have and wish to share in response to this post.

Hadden89

@darrenlschultz said in Chrome Web Store Blocked (Snapshot 2549.3):

is a single post in the Snapshot release thread [...] in the mass of all other replies [...] the proper or best means of promptly bringing to the attention of the Vivaldi developers an apparent bug as fundamental and disruptive as the total inability to access the Chrome web store?

Is not, actually. Only the bug report is. But I'm quite sure it was already reported|known. By the way, I tagged a team member in that post and more users then confirmed the issue so - even If I could have delayed the first report of the bug - the feedback of other people may helped to escalate the priority to fix the issue.

//edit: Tnx, I fixed the link @Pathduck

Pathduck

@darrenlschultz You did nothing "wrong" - it's just a good idea to check the release topic first to see if others have posted. In this case it was such an obvious bug that clearly affected all users so it was kind of redundant

And yes, I agree that there might be a little too much "frivolity" in the release threads. I'm certainly guilty of that... I consider at least the first page a bit of a free-for-all

I do think the team watches the Snapshot release topic, at least for the first couple days, in case any major regressions (like this) is reported.

Other than that, like @Hadden89 posted, the bug report form is the only way to get an issue to the developers. But be aware that unless you do proper testing beforehand and make good reproduction steps it will likely be closed as "not reproducible". The testers who do bug triage have only a short amount of time to spend testing each issue that comes in, so make that report good and detailed.

BTW @Hadden89 you posted the Italian link- "Ho bisogno di aiuto? Leggi le nostre linee guida su come segnalare bug e come segnalare arresti anomali."

DoctorG

The issue was already known in bug tracker.

DoctorG

Workaround:

If you leave the tab open and restart Vivaldi the Chrome Web Store is shown.

Pathduck

@doctorg Such a strange bug. It would be very interesting to have a bug post-mortem from the devs on what caused this weird blocking of the Chrome store when a fix is released.

Unless it's very embarrassing, like they were adding an exception for the adblocker and it turned out to do a full-document block instead

garyo

chrome.google.com is blocked.

Seems that the Vivaldi developers are not doing enough testing before releases. Bookmark renaming also broke in this release.

5.1.2549.3 (Official Build) (64-bit); Windows 11 Version 21H2 (Build 22000.434)

Pathduck

@garyo said in Chrome Web Store Blocked (Snapshot 2549.3):

Seems that the Vivaldi developers are not doing enough testing before releases.

Seems that some Vivaldi users are not doing enough reading to understand the purpose of a Snapshot release for testing and reporting bugs.
https://vivaldi.com/blog/snapshot-vs-stable/

iAN CooG

@garyo said in Chrome Web Store Blocked (Snapshot 2549.3):

Bookmark renaming also broke in this release.

I just renamed a bookmark and it works for me. I opened the bookmarks panel and I can rename the bookmarks both on the tree list directly or in the details below
You may want to be a bit more specific, describe step by step HOW you do it to get the issue.

DoctorG

A fix is In Progress today. Stay tuned.

DoctorG

@garyo said in Chrome Web Store Blocked (Snapshot 2549.3):

Seems that the Vivaldi developers are not doing enough testing before releases

It is so easy to blame others, isn't it? A testing (beta) version can have bugs and the "blocking" is not breaking the complete browser.
But i will tell you: testers found the issue and the bug was known before release and did not had got a fix.

There is a workaround for real world testers. Use it.

@garyo said in Chrome Web Store Blocked (Snapshot 2549.3):

Bookmark renaming also broke in this release.

Do not discuss your bookmarks issue here, wrong thread, post it there.

pafflick

@pathduck said in Chrome Web Store Blocked (Snapshot 2549.3):

It would be very interesting to have a bug post-mortem from the devs on what caused this weird blocking of the Chrome store

It was caused by a change in the Chromium source code (more on that here, if you're curious).

The fix has been issued internally already - expect it to arrive with the next Snapshot.

MinaWaheed9697

This message always appears when I try to open Google Chrome web store.
https://i.imgur.com/YEdZLa1.png

I tried the Guest mode, but the same issue happened.
I tried restarting Vivaldi and the same issue happened.

Vivaldi version: 5.1.2549.3 (Official Build) (64-bit)
OS: Windows 10 Pro

Pathduck

@pafflick That's great

Take your time though, I prefer my snaps with more than one (non-critical) bug fixed

Catweazle

@minawaheed9697 , the URL original is https://www.google.com/chrome/ and open without problems here.

hlehyaric

@minawaheed9697 This issue is known & already reported. According to @pafflick, a fix is expected in next Snapshot. Until then, you can use @DoctorG's workaround.

DoctorG

@minawaheed9697 This helps:
Open Extension Manager
Hit button Chrome Web Tore
Leave tab open (do not close!)
Restart Vivaldi
All nice.

/edit: @hlehyaric was faster.

pafflick

Here it is: Fix for the extension store – Vivaldi Browser snapshot 2553.3