fix(ios): fix sendMiFareCommand parameter and return value #84
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With the help of the react-native module: https://github.com/revtel/react-native-nfc-manager/blob/main/ios/NfcManager%2BMifare.m I was able to fix
sendMiFareCommand
to read out different memory banks from a mifare ultralight tag.Issue
Calling
mifare.sendMiFareCommand({data: [0x30,0x05]})
will run3000
inside the module so it will always read the first memory block. The 2nd parameter didn't change anything.Also the return event didn't include the actual data.
only the yellow part is read.
Fix
Using the methods from the react-native module I was able to convert the array to the correct parameter to read different memory slots.
Returning the
hex
value to the app.ti.nfc-iphone-4.1.1.zip