Describe the bug.
I'm not smart enough to figure out the exact issue, but I've noticed that the emulation support in Bettse's Seos app has been broken since this merge commit (on 28 June 2025). It still works perfectly on the latest commit of OFW, so I think it's a bug in the firmware, rather than the app.
The last commit it works correctly on is e3f7e1c. After that commit, the next one that builds is d174fa9 on which the app fails midway through communication with the reader (gives an authentication error). The next commit that changes the behavior is e64292d, which causes the app to no longer receive any data from the reader at all. The only event fed to the callback is Iso14443_4aListenerEventTypeFieldOff.
Reproduction
- Install Momentum Firmware
- Open the Seos Compatible app
- Select a saved Seos credential file and choose "NFC Emulate"
- Present Flipper Zero to Seos reader
Target
Flipper Zero
Logs
There aren't any logs other than the app saying "Field Off", which is printed by the callback and is caused by an `Iso14443_4aListenerEventTypeFieldOff`.
Anything else?
No response
Describe the bug.
I'm not smart enough to figure out the exact issue, but I've noticed that the emulation support in Bettse's Seos app has been broken since this merge commit (on 28 June 2025). It still works perfectly on the latest commit of OFW, so I think it's a bug in the firmware, rather than the app.
The last commit it works correctly on is e3f7e1c. After that commit, the next one that builds is d174fa9 on which the app fails midway through communication with the reader (gives an authentication error). The next commit that changes the behavior is e64292d, which causes the app to no longer receive any data from the reader at all. The only event fed to the callback is
Iso14443_4aListenerEventTypeFieldOff.Reproduction
Target
Flipper Zero
Logs
Anything else?
No response