Bebop

If you are trying to conduct a trade and the MetaMask extension is not being triggered, you've come to the right place. You may be experiencing one of the following issues:

(A) MetaMask is receiving the transaction, but something is keeping the extension from automatically being prompted to open on Bebop.

We've noticed issues with MetaMask not being triggered which have to do with how it interacts with other extensions (namely Revoke.Cash, Coinbase Wallet, Pocket Universe, Tally Wallet, &amp; a few others). This is likely due to something with the other extension that is inferring with Bebop. 

1. If you're using one of these extensions, please disable them as you initiate your trade to see whether this remediates the issue temporarily. 
2. We are aware of this issue and are looking for a way to prevent this from happening for any of our users.

If the error persists, please clear your browser's cookies and try again. This may be due to an issue on our end. 

1. We've noticed issues with MetaMask not being triggered which have to do with how it interacts with other extensions (namely Revoke.Cash, Coinbase Wallet, Pocket Universe, Tally Wallet, &amp; a few others). This is likely due to something with the other extension that is inferring with Bebop. 
 1. If you're using one of these extensions, please disable them as you initiate your trade to see whether this remediates the issue temporarily. 
 2. We are aware of this issue and are looking for a way to prevent this from happening for any of our users. 
2. If the error persists, please clear your browser's cookies and try again. This may be due to an issue on our end.

(B) MetaMask is receiving the transaction but something in your MetaMask settings is keeping the extension from automatically being prompted to open on Bebop.

Please try manually opening your MetaMask browser extension by clicking on the icon and confirming that the transaction is indeed showing in your MetaMask wallet. If it is, you can continue with the transaction manually or cancel the transaction and try again. To prevent this from happening in the future, please:

1. Ensure that your MetaMask wallet is enabled for all sites. 
   1. Open your MetaMask wallet extension settings. 
   2. Confirm that the wallet is set to read and change site data "on all sites" and not only "when you click on the extension".
   3. 
2.  Turn off auto-lock settings in MetaMask.
   1. Open your MetaMask wallet extension settings.
   2. Confirm that you do not have auto-lock enabled (which would be causing the wallet to lock every X minutes). 
3. If the error persists, please clear your browser's cookies and try again. This may be due to an issue on our end. 

1. Please try manually opening your MetaMask browser extension by clicking on the icon and confirming that the transaction is indeed showing in your MetaMask wallet. If it is, you can continue with the transaction manually or cancel the transaction and try again. To prevent this from happening in the future, please:
   1. Ensure that your MetaMask wallet is enabled for all sites. 
      1. Open your MetaMask wallet extension settings. 
      2. Confirm that the wallet is set to read and change site data "on all sites" and not only "when you click on the extension".
      3. 
   2.  Turn off auto-lock settings in MetaMask.
      1. Open your MetaMask wallet extension settings.
      2. Confirm that you do not have auto-lock enabled (which would be causing the wallet to lock every X minutes). 
   3. If the error persists, please clear your browser's cookies and try again. This may be due to an issue on our end. 

(C) MetaMask is not receiving the transaction from Bebop; when you open MetaMask manually there are no stacked transactions or notifications.

If the error persists, please clear your browser's cookies and try again. 

If you have attempted the above and are still having this problem, please report your issue to our team.

1. If the error persists, please clear your browser's cookies and try again. 
2. This may be due to an issue on our end. 
3. If you have attempted the above and are still having this problem, please report your issue to our team.