menu

Aragon

Aragon is the most powerful and modular way to run DAOs

Channels
# All channels
view-forward
# Announcements
view-forward
# App development
view-forward
# Aragon Agent
view-forward
# Aragon Client
view-forward
# Aragon Connect
view-forward
# aragonOS
view-forward
# aragonUI
view-forward
# Feature requests
view-forward
Team

Error from worker when I try to access any Aragon DAO on Chrome

May 28, 2020 at 5:34pm

Error from worker when I try to access any Aragon DAO on Chrome

May 28, 2020 at 5:34pm (Edited 1 month ago)
Hi
When I access any Aragon DAO on any Ethereum network using Chrome I get an Error from worker for [app]... error.
For example, if I go to this DAO I get the following:
Screenshot from 2020-05-28 19-27-39.pngScreenshot from 2020-05-28 19-30-30.png
There is no problem when I open DAOs in a different browser like Firefox.

May 28, 2020 at 6:05pm
Looks like there is a problem with every app's web worker. Could it be a conflict with one of your Chrome extensions?
  • reply
  • like
We're hotfixing this today—Chrome 83 current breaks the build and before we deploy the hotfix in a few hours, using Firefox will solve this :).
like-fill
1
  • reply
  • like
Ah! Seems like it was a good thing after all not to update Chrome on my laptop haha. Thanks If you want to follow the progress on the issue, here is the link: https://github.com/aragon/aragon/issues/1428
  • reply
  • like

May 29, 2020 at 8:52am
Oh I see. I'll be watching the issue then :).
  • reply
  • like
Ah, that is actually the wrong issue—#1428 is one about the fundraising app and it not handling a null value correctly.
This was fixed last evening (>12 hours ago); things should be all back to normal now!
like-fill
2
  • reply
  • like

June 2, 2020 at 7:26am
Yeah, it seems DAOs are working again. What dependencies do I have to update on my aragon projects so they can work on local?
Edited
  • reply
  • like

June 2, 2020 at 2:20pm
Hmm this is a bit problematic. Right now both our buidler plugin and CLI are pinned to a (pretty) old version of the client, because its local connectors do not work in newer versions.
Unfortunately it may be a while until we can update this properly, but this bug definitely increases the severity of the issue.
For local development, both Firefox and Brave will still work until we get this figured out.
like-fill
1
  • reply
  • like

June 3, 2020 at 9:23am
Oh ok. I'll use a different browser then.
Edited
  • reply
  • like