If you're having any issues while connecting to MetaMask or even after you've connected, this article will help you get rid of them. You should be able to find a solution for ALL MetaMask-related issues, but if nothing here works, please contact us.
- Transaction requests approved on Metamask no longer pop up on the Lattice screen
- Stuck at the "Looking for your Lattice..." screen on MetaMask
- "Failed to get accounts. Please forget the device and try again. Make sure you do not have a locked SafeCard inserted." error is shown on MetaMask
- The screen is stuck spinning on the "Loading - Connecting..." Lattice Connector page
Going through all these steps won't be necessary for most MetaMask issues as most should be fixed by re-connecting - the guide tells you explicitly when to try connecting to MetaMask again.
If you can't get transaction requests to pop up on your Lattice screen despite approving them in MetaMask, the first thing to check is whether both your computer and your Lattice are connected to the internet. This can also be the cause of getting stuck on the "Loading - Connecting..." page on the Lattice Connector.
You don't have to be connected to the same network, but both devices do have to be online. You can check your Lattice's connection status directly on the screen in the upper right corner (see the firmware reference article to know what icons to look for).
If you're sure you're online, move on to step 2.
The latest Lattice firmware version can always be found in this article. If you're not on the latest, just go to System Preferences → Software Update. If you cannot see an update available here, make sure your Lattice is online.
To update your MetaMask extension, follow the guides below:
- Chromium: right-click on the MetaMask icon and select Manage Extension. Then enable Developer mode in the top right corner and after that, just click on Update.
- Firefox: right-click on the MetaMask icon and select Manage Extension. In the gear icon menu in the top right, click on Check for Updates. If there are any updates available, install them.
If you're trying to connect a SafeCard wallet to MetaMask, the inserted SafeCard has to be unlocked prior to initiating the connection - MetaMask cannot import addresses from a locked card.
Trying to connect with the locked card will result in the "Failed to get accounts" error. Unlock your card and try again. If you're not connecting with a card or your card is unlocked, move on to step 3.
Make sure that you're typing in the correct device ID if you see the spinning wheel on the Lattice Connector page (this might also be caused by your Lattice being offline, but this part was written with the assumption that you made sure your Lattice is indeed online as per step 1).
You get a new device ID every time you reset the Lattice network module, but you can always find your active device ID in the last menu item on the Lattice homescreen.
If you've already connected to MetaMask with your Lattice and you want to e.g. connect a SafeCard wallet or import more addresses from your Lattice wallet, you need to use the same password you've used when this connection was created. If you forgot the password, you can move on to step 4 and attempt re-connecting.
If your Lattice is online, your inserted SafeCard is unlocked (if you're using one) and you're sure you're typing in the correct device ID and password combination but you're still having issues, it's time to try removing the old connection and re-connecting to get a fresh one.
5.1 Remove the MetaMask permission
Go to Permissions on your Lattice and if you see a MetaMask permission there, delete it.
5.2 Remove previously linked Lattice accounts from MetaMask
Next, remove all accounts with the Lattice1 tag in the list of accounts on MetaMask. You can do this by clicking on the three dots when you've switched to that account and then selecting the Remove account option.
5.3 Delete MetaMask cache
If you're using a Chromium-based browser such as Chrome, Brave etc., you can delete only hosted app data without deleting your cookies or browser cache. On Firefox, you'd have to clear all cookies and cache, so we only recommend this step for Chromium users and we suggest Firefox users try the next steps of this guide before clearing cookies and cache.
After you're done with steps 4.1-4.3, try connecting to MetaMask the usual way. If you still get stuck on the "Failed to get accounts" error, move on to the next step.
Most MetaMask issues will be resolved by re-connecting as described above, but there can be edge cases where you'll have to remove the MetaMask 3rd party connection from the Lattice Manager and reset app state.
- 2.Navigate to Settings, if you see MetaMask listed under Third Party Connections, click on Forget (if you don't see anything here, just move on to resetting app state)
- 3.Scroll down and click on Reset App State
After the Lattice Manager state is reset, make sure you go through step 4 again (just confirm you don't have a MM permission on your Lattice, Lattice1-tagged accounts on MM and delete the MM cache if on Chrome) and then try connecting to MetaMask again.
If everything else fails and you still somehow get stuck on a particular error, there's also the "nuclear" option of getting a completely fresh MetaMask instance installed before attempting to connect again. You will first have to remove the old MetaMask from your browser completely.
You will LOSE all accounts/addresses that are not backed on hardware. This means the default MetaMask hot wallet Account 1 will get erased, as well as any hot accounts you imported from a private key.
Because of this, you should make sure that removing MetaMask will not result in any unwanted consequences very carefully!
Removing MetaMask is fairly simple - just right click the extension and select "Remove from Chrome" or "Remove extension" on Firefox. Before installing MetaMask again, make sure you you removed the MetaMask permission from your Lattice and you can also reset app state on the Lattice Manager - just to be sure.
After you're ready to connect again, install MetaMask again:
If you still can't get this to work after going through all these steps, please create a ticket or reach out to us on our Discord server and we'll help you figure this out.
Last modified 1mo ago