Can’t sign Access Control Condition

  • Resolved notasausage

    (@notasausage)


    2 years, 6 months ago

    Signed an access control condition with my MetaMask wallet and get this error:

    An unknown error occurred when trying to get a signature from your wallet. You can find it in the console. Please email [email protected] with a bug report

    Each time I try and sign again, I just get the error.

    Console says:

    Expected null or array with at least one valid str…'. Received: https://blockscout.com/xdai/mainnet

    I’m attempting this via a locally hosted WordPress installation with the Local app from Flywheel. Going to attempt on the Staging site to see if that’s the issue…

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter notasausage

    (@notasausage)

    Local or Staging didn’t matter. Also noticing this error in the console:

    MetaMask - RPC Error: Unrecognized chain ID "0x64". Try adding the chain using wallet_addEthereumChain first.

    Attempting to token gate by POAP event ID, so both on xDai and mainnet ETH.

    Thread Starter notasausage

    (@notasausage)

    Well, I solved my own problem after rereading those console messages. Since POAPs are created on xDai but can be moved to mainnet, the Access Control Condition correctly checks for the POAP event ID token on either. Which means to actually sign that row, MetaMask needs to be setup for the xDai (Gnosis) chain so it can switch between chains and sign on both.

    That’s pretty easy to do, more info here: https://docs.gnosischain.com/tools/wallets/metamask

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Can’t sign Access Control Condition’ is closed to new replies.