Can not read/write tag after update to Android 17 [Pixel 8/910/Pro]

[monelli]

Phone: Google Pixel 8 Pro
App version 4.3.1

Android version: 17.0.0 (CP2A.260605.012, Jun 2026)

Display Tag Info works well.
Start Mapping and Read Tag doesn't work.

Output:
New tag found (UID:XXXXX)
7 keys loaded. Creating key map This might take a while
No valid key found in chosen key file

Same Tag and same key file in another phone work.

For me no app problem but google problem, like this: #441

Thank you!

[AnthoDingo]

Hello, same issue on Pixel 8 pro too but with July 2026 update.

[badtime]

Same issue with PIXEL 9 ANDROID 16 june 2026 update.

It has always worked well, but about three days ago it started trying to pair the keys (which previously worked perfectly) and failing to pair them.

[AnthoDingo]

I already test on Pixel 6 with Android 17 July 2026 update, and it works.

[bytevictor]

Same Issue w/ Pixel 9 with already checked keys

[MainKronos]

I can confirm I am experiencing the exact same issue on a Pixel 10 immediately after updating to Android 17.

Just like you described:

• Display Tag Info works fine and detects the tag.
• Mapping and Reading fails completely with the message "No valid key found in chosen key file".
• The exact same tag and key file work perfectly on other devices running older Android versions.

This definitely looks like an Android 17 platform regression/API change affecting the NFC stack rather than an issue with MCT itself.

[AnthoDingo]

Someone opened an issue on Android Bug Tracker https://issuetracker.google.com/issues/532592088

[nicof38]

Yes, and I did reported it here also : https://issuetracker.google.com/issues/530892371

If not too late for you, rollback of google play system is (or was ok for me 2 weeks ago) ok : https://flash.android.com/tools/google_play_system_update_rollbacks

[arthur-robog]

Hey
Same issue here on Pixel 8 pro with latest update

[guillaumelbf]

Hey everyone,

The latest system update for the Google Pixel 8/9/10 seems to have changed something related to key files (I don't know why).

We fixed the issue on my friend's phone (Google Pixel 8 Pro) by simply re-reading the tag with both std.keys and extended-std.keys enabled. After a while (because of the large number of keys), the tag was finally read successfully, and we were then able to save the new key file.

Weirdly, the new key file only contains FFFFFFFFFFFF, but it works now. He can read and write tags just like before.

[ikarus23]

Yes, seems to be an issue with Android 17. Have the same problem on my reference Pixel 10 Pro. Also other apps seam to suffer too: Reading an empty tag (´FFFFFFFFFFFF` keys) with NXP's TagInfo failed.

Strange observation: I can read empty tags when I chose the std.keys and the extended-std.keys. But not when I only chose std.keys. But not all the time. It is very odd. Somewhat similar to @guillaumelbf observation. But only for empty tags.

Did not have the time to debug further. Sorry. I'm (mostly) on vacation. It will be another ~2 months...