Troubleshooting Guide

Quick technical resolutions for common DApp node connectivity, mobile limitations, and token visibility issues.

1. “Buy via 🦊MetaMask” doesn’t open directly on iPhone?

This is due to default mobile browser limitations (such as iOS Safari) — the system policies may prevent standard web layouts from launching the external 🦊MetaMask app automatically.

Solution: Open your mobile 🦊MetaMask App directly → Tap the menu icon (≡) or side drawer → Select the integrated "Browser" feature → Enter the portal link: https://neoxcoin.github.io to execute flawless smart contract interactions.

2. Getting a “Network Not Supported” error?

This occurs when your active Web3 wallet extension or node configuration is mapped to an unsupported ledger layer.

Solution: Manually toggle your active wallet architecture to Base Mainnet. Alternatively, you can use automated toolkits like Chainlist to bind the parameters natively: Add Base Mainnet via Chainlist.

3. “🦊Add to MetaMask” button doesn’t work?

This custom injection sequence operates optimally on official MetaMask desktop extensions or directly inside 🦊MetaMask’s built-in mobile browser shell. Standard mobile system apps systematically block script alerts.

Tip: You can completely bypass this limitation by navigating to "Import Tokens" inside your asset management panel and manually pasting our verified specifications:

  • Token Contract Address: 0x80AD039927cDf2341c1428b0BAFB8D3421dc122e1
  • Token Symbol: NXC
  • Decimals of Precision: 18

4. Can’t see your NXC after a successful purchase?

Your cross-border transaction log may still be pending validation in the public L2 mempool registry, or the custom token structure hasn't been mapped onto your active asset tracker tab yet.

Solution: Simply refresh or restart your MetaMask utility instance. If balance updates remain latent, reference the exact smart contract configurations listed in "Step 3" above to import your holdings securely.