-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
MOD-2833 : Add properties, events and method for TagTechnologyNfcV (ISO15693) #46
base: NativeTagSupport
Are you sure you want to change the base?
MOD-2833 : Add properties, events and method for TagTechnologyNfcV (ISO15693) #46
Conversation
@fasihul-axway Please review this PR. |
|
4dd5487
to
8fdee8b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@anil-shukla-axway, please add api documentation, i do not see any YML document with this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@anil-shukla-axway, please see my comment, i think some code refinement required before merging this PR. Once you done with changes, please update YML accordingly.
uint8_t requestFlags = [requestFlagsValue unsignedCharValue]; | ||
|
||
[[self.tagProxy asNFCISO15693Tag] getMultipleBlockSecurityStatusWithRequestFlag:requestFlags | ||
blockRange:NSMakeRange(0, 8) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why using hardcoded blockRange? As per apple documentation range should be "The range of blocks. Valid start index range is 0 to 255 inclusively. Valid length is 1 to 256 inclusively."
https://jira.appcelerator.org/browse/MOD-2833