Troubleshooting

Fix common issues with the Morsel extension, mobile app, dApp connections, and transactions.

This guide covers the most common issues users and developers encounter with Morsel. If your issue is not listed here, reach us on Discord.

Extension Not Detected by a dApp

  • Make sure Morsel is installed and enabled in your browser extensions (chrome://extensions)
  • Refresh the dApp tab after installing — most sites only check for providers on page load
  • Check that the extension is not disabled or in developer mode with an error
  • Try in a fresh browser profile to rule out conflicts with other wallet extensions
Some dApps only check for window.solana on load. If Morsel loads after the page, it will be missed. A hard refresh (Ctrl+Shift+R) usually fixes this.

Connect Popup Not Appearing

  • Check your browser for blocked popups — Morsel opens its approval window as a popup
  • Make sure you are not in an iframe context, which blocks extension popups in some browsers
  • Try calling provider.connect() from a user interaction (click event), not on page load
  • Disable other wallet extensions temporarily to check for conflicts

window.morsel is undefined

The provider may not be ready when your code runs. Always detect after the page loads:

javascript
window.addEventListener('load', () => {
  const provider = window.morsel ?? window.cookie ?? window.solana;
  if (!provider) {
    console.log('Morsel not installed');
  }
});
If you are using a framework like React or Vue, run detection inside a useEffect or mounted hook, not at the module top level.

Transaction Stuck or Pending

  • Cookie confirms in under a second — a stuck transaction usually means a network connectivity issue
  • Check your internet connection and try again
  • Open the transaction in Cookiescan (cookiescan.io) using the signature to see its on-chain status
  • If the transaction was never submitted, it will not appear on the explorer — try resending

Wrong Chain Sent

  • Both Cookie and Solana use the same address format — always check the token you are sending, not just the address
  • COOK sent on the Solana network and SOL sent on the Cookie network cannot be recovered — double-check the token before confirming
  • When in doubt, tap the token name in the Send screen to confirm which chain it belongs to

NFT Not Showing

  • Spam or unverified NFTs are automatically hidden — tap the Hidden section at the bottom of your NFT gallery to see them
  • Some NFTs take a few minutes to index after minting or purchase
  • If the NFT metadata image returns a 404, the artwork will not display but the NFT is still in your wallet

Swap Failing

  • Try increasing slippage to 1–2% for tokens with lower liquidity
  • Make sure you have enough COOK or SOL to cover the network fee (separate from the swap amount)
  • Some tokens have transfer fees — check the token details before swapping

Seed Phrase Import Not Working

  • Make sure you are entering the words in the correct order, separated by spaces
  • Check for typos — each word must be an exact match from the BIP39 word list
  • Morsel supports 12 and 24-word phrases — do not mix or truncate
  • If you imported from Phantom or another Solana wallet, the same seed phrase works in Morsel — your accounts will load automatically

Biometrics Not Working

  • Biometrics require device-level Face ID or fingerprint to be configured in your phone settings first
  • If biometrics fail 5 times, Morsel falls back to PIN — enter your PIN to re-enable biometrics
  • On desktop (Chrome extension), biometrics are not available — PIN only

Mobile App Crashing or Freezing

  • Force-close the app and reopen it
  • Make sure you are running the latest version from the App Store or Google Play
  • If the issue persists, clear the app cache (Android: Settings → Apps → Morsel → Clear Cache)
  • Your funds are safe — they are on-chain. Reinstalling Morsel does not lose funds as long as you have your seed phrase

Still Stuck?

Reach the team on Discord or open an issue on GitHub. Include your browser version or app version (found in Settings), your device, and a description of what you tried.