Considerations and Limitations

Consider these guidelines and limitations when developing features that use the NFCService API.

Device Limitations

In Android 11 or later, if the user denies permission to access NFC functionality more than one time during the app’s lifetime of installation on a device, the user won’t see the system permissions dialog again. Tapping Deny multiple times implicitly chooses the “don’t ask again” option.
In previous versions of Android, users see the system permissions dialog each time the app requested permission unless the user had previously selected “don’t ask again”. This change in Android 11 discourages repeated requests for permissions that users have selected to deny.
If the user has denied permission to access NFC functionality and must change their permissions to allow access, they can do so in their device’s settings.

Development Considerations

NFCService requires access to NFC hardware. To test NFC interactions during development, use actual, physical devices.

NFCService allows for an action that, if used irresponsibly or incorrectly, can lead to irreversible consequences for your users. This dangerous action is the capability to erase NFC tags from a mobile device.
As with all mobile capabilities, implementation of NFCService’s functionality, dangerous actions included, is at your discretion. Use caution when using dangerous actions in your component.
Note

NFCService Considerations

The NFCService plugin only interacts with NFC tags that are compliant with the NFC Data Exchange Format (NDEF) standard.
NFCService is built on top of mobile operating system and device features. NFCService’s capabilities therefore depend on Android or iOS features, which are subject to change beyond our control. When mobile operating system features change, the behavior of NFCService can change without notice.