-
Notifications
You must be signed in to change notification settings - Fork 195
Error publishing profile #547
Comments
Here people are having the same problem with similar stack traces: web3/web3.js#1916 |
@nick @tyleryasaka Any idea what the issue could be ? Also CCing @micahalcorn |
web3's |
@tyleryasaka: @sparrowDom is done for the day since it is already late in Europe... Would you be ok working on a fix this afternoon ? thanks in advance. |
Ok I don't think it's the problem I suggested in the previous comment. Confirmed the error is coming from this line: https://github.com/OriginProtocol/origin-js/blob/staging/src/contractInterface/users/v00_adapter.js#L159 |
Reading through the issue @sparrowDom linked to, I'm not sure what we can do about this. We could roll back web3 to beta.34 but that would introduce breaking changes. This is not a bug on our end. This is what happens when we try to use beta software in production. 😬 |
The other possibility is that we can change our event signature to not have all indexed parameters. See web3/web3.js#1916 (comment) |
This fix should help with this issue: OriginProtocol/origin-js#530 |
When you change your profile information and/or attestations and try to publish them the following error with no metamask confirmation is thrown:
(this happens on staging environment on Rinkeby)
The text was updated successfully, but these errors were encountered: