2025-09-22 5:37 PM - edited 2025-09-23 12:28 AM
Hi,
I am working on a React Native project for an NFC app that needs to run on both iOS and Android. I am using the react-native-nfc-manager library to perform NFC operations. The NFC tag I am using is ST25DV, which supports NDEF and NfcV (ISO15693) technologies.
Some basic functionalities the app would perform are reading and writing raw memory blocks to the memory.
I noticed when I am using iOS device to perform read write operation, it can do so while keeping the tag intact with iOS device. I don't have to practically take the tag away from device and bring it near again to start the new nfc session.
In case of Android, to perform the writing functionality, I have to first send the command from device by pressing button, then device will start looking for NFC tag. I bring the NFC tag near the device; it detects it and locks in the session and sends the command to the tag and closes the session. Thats how the code is written.
Now if I want to read back from the tag, I press the read button and it starts looking for the tag. But I have to take the tag away from the device and bring it near to the device again for the device to detect the tag and send the new command.
The surprising thing is that ST's proprietary app in Android doesn't operate this way. You can keep the tag near to device and it will perform different operations without ever taking the tag away from device.
Is this limitation of React Native or just the Android device?
2025-09-23 12:24 AM
Is your question related to iOS or Android?
Your subject mentions iOS, but it seems the issue is occurring on Android. Could you please confirm?
2025-09-23 12:27 AM
Its on Android. Sorry I got it wrong in the title.