Error When Attempting to Modify an Asset Post-Publication

Wallet Address:
base:0x5c95455C5006E18f53f1a02d55B61Bd0bf93a0CA

Summary of the Issue:
I encountered an error when trying to modify an asset that I previously published using a contract created on Manifold (with a Safe multising wallet). The system fails to sync the information with the blockchain and throws an error.

What Are You Trying to Do?
I am attempting to modify an asset (edit metadata) that was already published in a Manifold contract.

What Is the Actual Outcome?
When I try to save and publish the changes, I receive the following error message:

Error Saving and Publishing: missing revert data in call exception; Transaction reverted without a reason string [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (data=“0x”, transaction={“to”:“0x94621Eab3427Cad734B14F7ffe4531398DF893FB”,“data”:“0xbb3bafd60000000000000000000000000000000000000000000000000000000000000002”,“accessList”:null}, error={“reason”:“processing response error”,“code”:“SERVER_ERROR”,“body”:”{"error":{"code":-32004,"message":"Not allowed"}}”,“error”:{“code”:-32004},“requestBody”:”{"method":"eth_call","params":[{"to":"0x94621eab3427cad734b14f7ffe4531398df893fb","data":"0xbb3bafd60000000000000000000000000000000000000000000000000000000000000002"},"latest"],"id":42,"jsonrpc":"2.0"}”,“requestMethod”:“POST”,“url”:“https://base.bridge.manifoldxyz.dev/rpc”}, code=CALL_EXCEPTION, version=providers/5.7.2)

The asset’s data does not sync with the blockchain.

Screenshot of the Issue/Error with Console:

Browser:
Microsoft Edge for business
VersiĂłn 127.0.2651.98 (CompilaciĂłn oficial) (arm64)

Wallet:
Owner of the contract: Safe Multisign wallet for creating the contract
One of the admins of the contract: Metamask wallet (the one posted at the beginning of this post)

please do not message anyone on telegram (see Forum Safety Guidelines: 🦺 Beware of External Support Links being shared) ; the above is a scam. we are looking into this and will update you on the forum.

1 Like

Hi, can you try again right now? we pushed a change recently that should have fixed this.