We are using the new NFC write functionality of iOS 13 to write data to a MiFare Ultralight NFC-tag, and it's working perfectly using the writeNDEF method
But as we are using the password protection feature of the NFC-tag we need to send the send the NDEF messages via the lowlevel method sendMiFareCommand
We have not been able to find any documentation for how to transform the NDEF format into the lowlevel data needed for the sendMiFareCommand-method
Any example or documentation on this for Swift would be greatly appreciated.
You might consider first unlocking the tag with a specific MIFARE command and then using the tag.writeNDEF() function on that. This can be accomplished in the same NFC Tag Session without terminating it. This will keep the tag unlocked in the meantime.
Review the Ultralight data sheet for instructions on PWD_AUTH. Code is 0x1B for Ultralight EV1 and newer. Section 1.8, page 30 shares instructions on specific use.
https://www.nxp.com/docs/en/data-sheet/MF0ULX1.pdf
Related
I'm just getting into NFC Tags for iOS and I want to program a contact record into an NFC tag so that it can be read by an iPhone that supports Background Tag Reading. It seems like Background Tag Reading in iOS only supports universal links and certain URI/URL messages. This is the link I read for reference:
Background Tag Reading Support Info
I know that Android supports the NDEF VCard Record Type, where one can then program a tag with a contact's info, and then scan and add that contact. I noticed that when I used the same tag with Apple, nothing showed up, so that's why I am assuming Apple doesn't support this NDEF Record type.
First off, am I correct in this information so far? Apple does not support NDEF VCard Records?
If that's true, is there any way to program a contact in or is the closest I'm going to get to a contact through the use of the tel:+14085551212 url, as stated by the link above?
Yes only URIs are identified by iOS. For v-Card you must use a third party app. The app I made for example can handle v-Cards. https://apps.apple.com/us/app/nfc-for-iphone/id1249686798
Apple might open this in the future but who knows...
This can be achieved using URL NDEF record itself. Just host a vcard on a URL and use that for URL NDEF record. Scanning the tag will trigger browser, and opening it will open the contact application with the details in the vcard loaded.
Note the URL should have VCARD content, and content type header should be text/x-vcard. You can create one using service like www.vcard.link
We started to develop a strong use-case with NFC-compatible Wallet Passes, but we got stuck at one point. We already created an NFC pass and stored it into an iPhone's Wallet, so now we want to read out the NFC content (what is provided in the "message" key in the NFC dictionary; reference: https://developer.apple.com/library/archive/documentation/UserExperience/Reference/PassKit_Bundle/Chapters/LowerLevel.html). How can we do it with a standard NFC reader, like an ACR1255u-J1?
There is a video from a working demo: https://www.youtube.com/watch?v=XhmKxKpU4x4 -- they successfully read out the membership pass content somehow.
As we don't have NFC certification for creating passes, we used a pass from PassNinja's example, which has an "encryptionPublicKey". Is this the reason why we can't read out the content? I tried to read out the content via ACR1255u-J1, a standard PCSC driver, and this package's first example: https://www.npmjs.com/package/nfc-pcsc
The first example of the linked repository represents the code that I used for the first tests.
The NFC reader can read all of the standard tags, but can't read an iPhone tag. The error message is: "Tag not compatible with AID F222222222."
I need to share the text or image from one ios app to Yammer social network.
I am able to do login using iOS SDK of Yammer but not getting how can I share text or image from ios app to Yammer. I got the code to share text from browser but not from application.
Anybody has any idea??
Thanks in advance for your help and efforts.
This is documented on the Yammer API page. In order to post text and attach image
https://developer.yammer.com/v1.0/docs/messages-json-post
Parameters:
body - The text of the message body.
attachmentn and pending_attachmentn - Yammer provides two methods to associate attachments with a message. Both make use of multi-part HTTP upload (see RFC1867).
The first method is the easiest, simply use file form elements with names attachment1 through attachment20. If there are a several attachments or the attachments are large it may take some time for a message to POST causing your application to appear to hang.
An alternative way is to use the Pending Attachments resource (see below for details) allowing attachments to be uploaded in parallel. Apps that support HTTP chunked transfer encoding can monitor the progress of each upload. On success each pending attachmentâs response body includes an id. These pending attachment ids are to be submitted with the message using form elements pending_attachment1 through pending_attachment20. Finally, if form elements for both attachmentN and pending_attachmentN are present only the pending_attachmentN elements will be honored.
I never used Yammer, but I wrote another app like Yammer used the given API, Yamme site should provide an API to share.
As a new feature in iOS 8, the Mail app will now display a dialog at the top of the screen with the contact information that is automatically pulled from within the email (generally the signature of the sender). A quick example of this feature is posted below (taken from Ars Technica's iOS 8 review available here):
After looking several emails with a variety of different email signatures, it seems that this feature has rather narrow requirements in order for the information to be successful extracted. Does anyone know what these restrictions are or how to format a signature so that it will always be picked up by Mail?
Has anyone been able to open the foursquare app directly from an NFC tag? If yes, what custom URL do you write onto the tag?
For android, a simple http://m.foursquare.com/venue/VENUE_ID does the trick.
The same url format works for BlackBerry devices. The only thing that may be different is the formatting of the NFC tag itself. It needs to be an NDEF tag with a record type of "U". The Android app also will read tags of that format.