Why an NFC tag will not write on iPhone

“The phone detected the tag” and “the tag is writable” are different states. A reliable diagnosis keeps detection, connection, NDEF support, writable status, capacity, payload validation, and the final write result separate.

Start with the status, not repeated tapping

Apple’s NDEF write flow connects to the detected tag and calls queryNDEFStatus. The response identifies whether the tag is unsupported, read-only, or writable and reports the maximum NDEF message size.

Use the result to choose the next action:

• Unsupported: the detected object does not expose a writable NDEF interface for this workflow. Use a compatible public NDEF tag.
• Read-only: the tag cannot accept another message. Replace it unless its existing content is already correct.
• Writable but too small: shorten the payload or choose a higher-capacity tag.
• Writable with enough capacity: inspect payload validation and the physical scan conditions.

Check the payload before the radio session

Boreal NFC blocks empty values and malformed values for templates that expect URLs, email addresses, or phone numbers. A format warning should be resolved before repeatedly presenting a physical tag.

For public destinations, prefer a stable HTTPS URL. It is easier to test and usually smaller than embedding all destination data directly in the tag.

Remove other NFC tags from the area

If more than one tag is near the antenna, the reader may not have a single unambiguous target. Separate stacks of unused stickers or cards and present one tag at a time.

Reposition and retry deliberately

Keep the tag near the iPhone’s NFC antenna for the full session. Cases, metal surfaces, tiny antennas, damaged inlays, and final installation materials can reduce reliability. If a bare tag works but the installed tag fails, treat placement as the changed variable.

Know the product boundary

Boreal NFC reads and writes public NDEF records. It does not clone payment, transit, access, hotel, secure identity, or protected card systems. A protected credential failing to expose editable NDEF data is not a Boreal NFC write bug.

Accept the result with a read-back

After the app reports a successful write, scan the tag again and compare the decoded value with the intended value. Then open the destination and test the installed item on representative receiving devices.

Sources and review

• Apple: Building an NFC Tag-Reader App
• Apple: NFCNDEFTag interface
• Boreal NFC 1.0.5 status and retry behavior reviewed August 12, 2026.

If the tag choice is uncertain, compare NTAG213, NTAG215, and NTAG216.