Re: [web-nfc] New Tag Scanned problems from PWA (#674)

Findings so far:

I asked a colleague to borrow his phone (Galaxy 25, Android Version 16) and his phone was not able to scan the tag I had at all with the same NFC settings I have on my Galaxy 22 device. This lead me to think that perhaps the issue is with the tag.

I am using the app NFC Tools to get information about my tag. The tag in question is of tag type **ISO 15693 (NXP - ICODE SLIX)**. It has technologies available: **NfcV, Ndef**.

I read in the w3c documentation (https://w3c.github.io/web-nfc/#ndef-compatible-tag-types) where you have the list of compatible tag types. My tag is of type **NFC Forum Type 5**. It should be supported.

But it seems that things changed with Android version 15 and version 16:

1. **Android v15 introduces a new NFC Tag Permission System,**
Apps must be explicitly allowed (by user or policy) to receive certain tag technologies.
The OS now evaluates tag type, protocol, and data format before sending it to the app.
Some tag types (including ISO 15693) are considered “restricted” unless explicitly allowed.

2. **Android 16 added the “New Tag Scanned” popup as part of this system**
The popup appears when:
A tag is detected
But the system needs user confirmation before routing it to an app
OR the app is not on the allow-list

3. **Chrome’s Web NFC is NOT updated for the new Android NFC rules**
**Web NFC on Chrome:** 
Was designed for NFC-A/B (NTAG, Mifare, etc.)
Has partial, unofficial support for NFC-V under old Android APIs
Has not yet been updated to request the new required permissions
Therefore: Web NFC is now “blocked” from ISO 15693 tags on many phones

These last Android v15 and v16 bullets were something I wrote with ChatGPT about, so keep that in mind about the accuracy of them. But from what I gathered elsewhere on the net, there seems to be some truth to it at least.

TL:DR, It seems some devices (Galaxy 22, Android V16) can scan my tag and get the "New Tag Scanned" error while others (Galaxy 25, Android V16) cannot scan it at all. There seems to be some inconsistencies when using web-nfc across Android devices on Chrome from V15+. It might be related to the tag type.

Is there something you can recognize here? Ill continue to look into getting different devices and testing further on my tag



-- 
GitHub Notification of comment by SIREtheKnight
Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/674#issuecomment-3606773034 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 3 December 2025 13:07:28 UTC