Core NFC in Xamarin.iOS

Reading Near Field Communication (NFC) tags using iOS 11

CoreNFC is a new framework in iOS 11 that provides access to the Near Field Communication (NFC) radio to read tags from within apps. It works on iPhone 7, 7 Plus, 8, 8 Plus, and X.

The NFC tag reader in iOS devices supports all NFC tag types 1 through 5 that contain NFC Data Exchange Format (NDEF) information.

There are some restrictions to be aware of:

  • CoreNFC only supports tag reading (not writing or formatting).
  • Tag scans must be user-initiated, and time-out after 60 seconds.
  • Apps must be visible in the foreground for scanning.
  • CoreNFC can only be tested on real devices (not on the simulator).

This page describes the configuration required to use CoreNFC and shows how to use the API using the "NFCTagReader" sample code.


To enable CoreNFC, you must configure three items in your project:

  • An Info.plist privacy key.
  • An Entitlements.plist entry.
  • A provisioning profile with NFC Tag Reading capability.


Add the NFCReaderUsageDescription privacy key and text, which is displayed to the user while scanning is occurring. Use a message appropriate for your application (for example, explain the purpose of the scan):

<string>NFC tag to read NDEF messages into the application</string>


Your app must request the Near Field Communications Tag Reading capability using the following key/value pair in your Entitlements.plist:


Provisioning Profile

Create a new App ID and ensure that the NFC Tag Reading service is ticked:

Developer Portal New App ID page with NFC Tag Reading selected

You should then create a new provisioning profile for this App ID, then download and install it on your development Mac.

Reading a Tag

Once your project is configured, add using CoreNFC; to the top of the file and follow these three steps to implement NFC tag reading functionality:

1. Implement INFCNdefReaderSessionDelegate

The interface has two methods to be implemented:

  • DidDetect – Called when a tag is successfully read.
  • DidInvalidate – Called when an error occurs or the 60 second timeout is reached.


In the sample code, each scanned message is added to a table view:

public void DidDetect(NFCNdefReaderSession session, NFCNdefMessage[] messages)
    foreach (NFCNdefMessage msg in messages)
    {  // adds the messages to a list view
    DispatchQueue.MainQueue.DispatchAsync(() =>

This method may be called multiple times (and an array of messages may be passed in) if the session allows for multiple tag reads. This is set using the third parameter of the Start method (explained in step 2).


Invalidation can occur for a number of reasons:

  • An error occurred while scanning.
  • The app ceased to be in the foreground.
  • The user chose to cancel the scan.
  • The scan was cancelled by the app.

The code below shows how to handle an error:

public void DidInvalidate(NFCNdefReaderSession session, NSError error)
    var readerError = (NFCReaderError)(long)error.Code;
    if (readerError != NFCReaderError.ReaderSessionInvalidationErrorFirstNDEFTagRead &&
        readerError != NFCReaderError.ReaderSessionInvalidationErrorUserCanceled)
      // some error handling

Once a session has been invalidated, a new session object must be created to scan again.

2. Start an NFCNdefReaderSession

Scanning should start with a user request, such as a button press. The following code creates and starts a scanning session:

Session = new NFCNdefReaderSession(this, null, true);

The parameters for the NFCNdefReaderSession constructor are as follows:

  • delegate – An implementation of INFCNdefReaderSessionDelegate. In the sample code, the delegate is implemented in the table view controller, therefore this is used as the delegate parameter.
  • queue – The queue that callbacks are handled on. It can be null, in which case be sure to use the DispatchQueue.MainQueue when updating user interface controls (as shown in the sample).
  • invalidateAfterFirstRead – When true, the scan stops after the first successful scan; when false scanning will continue and multiple results returned until the scan is cancelled or the 60 second timeout is reached.

3. Cancel the scanning session

The user can cancel the scanning session via a system-provided button in the user-interface:

Cancel button while scanning

The app can programmatically cancel the scan by calling the InvalidateSession method:


In both cases, the delegate's DidInvalidate method will be called.


CoreNFC enables your app to read data from NFC tags. It supports reading a variety of tag formats (NDEF types 1 through 5), but does not support writing or formatting.