Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NFC: Equivalent of NfcWorkerEventSuccess from before NFC refactor #3638

Open
GMMan opened this issue May 6, 2024 · 0 comments
Open

NFC: Equivalent of NfcWorkerEventSuccess from before NFC refactor #3638

GMMan opened this issue May 6, 2024 · 0 comments
Assignees
Labels
NFC NFC-related Triage Issues under initial investigation

Comments

@GMMan
Copy link
Contributor

GMMan commented May 6, 2024

I'm finally getting around to updating my app that uses the old NfcWorker API to NfcListener, and I can't seem to find the equivalent of NfcWorkerEventSuccess. I was looking at NfcEventTypeRxEnd to add a hook for checking if something has changed, but it doesn't look like all events are propagated down to the callback fed to nfc_listener_start(). In particular, I'm using the Mifare Ultralight listener, and the only event it seems to propagate is MfUltralightListenerEventTypeAuth, which isn't very useful in my case. Is there some way I can detect that a write has occured to the emulated tag?

Also, just to confirm, when checking data I should be using nfc_listener_get_data() and commit back to the NFC device using nfc_device_set_data()? Or does the architecture guarantee that I can just use nfc_device_get_data() directly (with the same protocol specified in nfc_listener_alloc(), of course)? Just noticed its NfcDevice is internal, so I'll definitely have to do something different...

@hedger hedger added NFC NFC-related Triage Issues under initial investigation labels May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NFC NFC-related Triage Issues under initial investigation
Projects
None yet
Development

No branches or pull requests

3 participants