That looks a super hacky way of trying to enable Mifare Classic support when the phone does not support it and it won't fix all devices.īut your problem is the hack relies on modifying the Tag Object that your App has created from the Intent when you are using the old API enableForegrounDispatch If (Array.IndexOf(techList, "") > -1) ") Mifare Classic tag authentication failure: 8250A9B9 I've checked the Mifare Classic Tool source code to see what else it's doing and borrowed the patchTag logic (it didn't help!). As soon as I've detected any tag with the Mifare Classic Tool my code works perfectly every time.
On most devices it works perfectly every time, but on a Unitech EA510 the authentication consistently fails UNLESS I first read the card using the Mifare Classic Tool ( ).
I'm trying to read user data from sector 0 block 1 of Mifare Classic cards in a Xamarin Forms Android app.
0 kommentar(er)
