Posts

Post marked as solved
21 Replies
I am using swift language and testing on an iPhoneXS. Here is an example of customCommand usage:tag.customCommand(requestFlags: [.highDataRate], customCommandCode: 0xAE, customRequestParameters: Data(bytes: [UInt8(0x0D), UInt8(0x01)], count: 2), completionHandler: { (response: Data, error: Error?) in //completion handler })
Post marked as solved
21 Replies
Hi d.Knowles,Yes I do have the latest (beta 5 build 17A5547d), and XCode 11.0 beta 3. When do you get the error ? At the start of the session or when you actually call the customcommand function?If you are getting the error before the end of tag connection, you should check again your App profile, capabilities, .plist and .entitlements file and that you ar embedding the corenfc.framework library ... ( see Core NFC Enhancements - WWDC 2019 - Videos - Apple Developer )If the connection goes well but you still get the error on customcommand, the problem should be solved with installing beta 4 or later and I did actually get the confirmation from the 'Feedback Assitant'.I just needed the customcommand function as I am using the NFCISO15693Tag to communicate with and ST25DV Tag. I have not tested the other functions.
Post marked as solved
21 Replies
I reported this problem using the 'Feedback Assistant' .The report status has just changed to :Resolution:Potential fix identified - For a future OS updateI hope that this is going to be in the coming beta update ...