Having trouble scanning a tag, writing your own NFC tag, or placing tags on metal surfaces? Start here. This page covers the most common TapNota setup issues and how to fix them fast.
Most NFC issues come down to one of five things: bad phone position, unsupported device settings, incorrect tag writing, metal interference, or a damaged/locked tag.
The NFC antenna is not always in the center of the phone. On many phones it is closer to the top back area. Move the phone slowly across the tag and hold it there for 1–2 seconds.
Many Android phones require NFC to be enabled in settings. iPhone support depends on the model and how the tag is being used. Some devices support quick background reading, while others are more limited.
If possible, scan the tag before sticking it permanently onto a tool, machine, shelf, or asset. This helps you tell the difference between a bad tag and a bad mounting surface.
If you are writing your own tags, confirm the tag contains the full TapNota URL and that it was written as an NFC NDEF record, not just partial raw text. Android’s NFC docs specifically distinguish NDEF handling from lower-level tag access.
Standard NFC tags often perform poorly on metal or may not work at all unless they are made for metal surfaces. If your tag is going on a metal tool, panel, rack, machine, or vehicle, use an on-metal / anti-metal NFC tag or a proper foam/ferrite-backed tag.
If one phone does not scan the tag, test with another NFC-capable phone. That quickly helps isolate whether the problem is the tag or the device.
Try these in order:
If it scans off the object but not on the object, the issue is usually the mounting surface, not TapNota.
If you are using your own NFC tags, the safest method is to write the full TapNota URL using an NFC writer app on a phone or a dedicated NFC writer/encoder device. The important part is that the tag is written correctly as an NDEF URL record, not just random text or a broken partial link. Android’s documentation treats NDEF as the standard path for common tag reading/writing workflows.
If one tag works and another does not, the bad one may have been written incorrectly, locked, or be a lower-quality tag.
Standard NFC tags often lose performance when placed directly on metal because metal interferes with the NFC field. If your tag is going on a metal object, you usually need an on-metal or anti-metal tag, or a tag with the proper isolating layer behind it.
If your workflow depends on tags living on metal, buy the right style from the beginning. This is one of the most common real-world NFC mistakes.
That usually points to a device-specific issue, not a TapNota issue.
Always test with at least two phones before assuming the tag is defective.
This usually means the tag was written with the wrong URL or was overwritten at some point.
Possible causes:
Test the tag away from the object. If performance improves, the environment is the issue. If not, replace the tag.
Not always. For best compatibility, use common NFC Forum tag types and reputable NFC tags. NXP’s NTAG21x line is a standard Type 2 family commonly used in mass-market NFC applications, which is why many NFC products are built around those chips.
This saves a lot of frustration, especially with metal assets and bulk deployments.
These are the questions most people ask when they are setting up TapNota for the first time.
The most common causes are: NFC is off, the phone is not positioned over the antenna correctly, the case is interfering, the tag is on metal, or the tag was written incorrectly.
Use an NFC writer app on a phone or a dedicated NFC writer/encoder, and write the full TapNota URL as an NDEF URL record. That is the cleanest and most compatible setup for standard phone scanning workflows.
No. Many standard NFC tags are not designed for direct metal mounting. Use an anti-metal or on-metal NFC tag when applying tags to tools, machines, racks, vehicles, or other metal surfaces.
No. Many modern phones do, but not all models support NFC the same way. Android and iPhone behavior can vary by device and OS support.
Yes. Always test the tag first, then test it again after mounting it on the real object. That is especially important for metal surfaces and thicker materials.
The tag was likely written with the wrong URL, partially written, or overwritten later. Rewrite it with the correct TapNota URL and test immediately after writing.
That usually means weak placement, poor-quality tag material, metal interference, or a phone positioning issue. Test it with another phone and test the tag away from the surface.
Standard NFC Forum-compatible tags from reputable vendors are the safest starting point. NXP’s NTAG21x family is a common example used across many mass-market NFC tags.